DOC: Fix PEP-8 issues in timedeltas.rst
 - Replace `from pandas.tseries.offsets import *` with `pd.offsets.<ClassName>` for better readability.

# [Codecov](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=h1) Report
> Merging [#23905](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=desc) into [master](https://codecov.io/gh/pandas-dev/pandas/commit/a7b187ab42c48342478ed8664145f21578f50622?src=pr&el=desc) will **not change** coverage.
> The diff coverage is `n/a`.

[![Impacted file tree graph](https://codecov.io/gh/pandas-dev/pandas/pull/23905/graphs/tree.svg?width=650&token=eZ4WkYLtcO&height=150&src=pr)](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=tree)

```diff
@@           Coverage Diff           @@
##           master   #23905   +/-   ##
=======================================
  Coverage   92.29%   92.29%           
=======================================
  Files         161      161           
  Lines       51498    51498           
=======================================
  Hits        47530    47530           
  Misses       3968     3968
```

| Flag | Coverage Δ | |
|---|---|---|
| #multiple | `90.69% <ø> (ø)` | :arrow_up: |
| #single | `42.43% <ø> (ø)` | :arrow_up: |


------

[Continue to review full report at Codecov](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=continue).
> **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta)
> `Δ = absolute <relative> (impact)`, `ø = not affected`, `? = missing data`
> Powered by [Codecov](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=footer). Last update [a7b187a...6bc4ce5](https://codecov.io/gh/pandas-dev/pandas/pull/23905?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments).
 This looks fine to me.  Only question is if the importing of Second/Minute etc is intentional. Not sure what you mean. Replacing the `from pandas.tseries.offsets import *` and using the full path version of `Second`... is intentional, as importing `*` is discouraged in Python, and having the full path makes things clearer IMO, as the user know where `Second` and the rest are coming from. Is this what you mean? I would have a strong preference against `*` imports in actual python code, but the .rst files I'm not so familiar with, don't know if separate conventions apply there. Well if someone reads the documentation finding something like `Second(...)` it's not clear what that class is. Is it a pandas class, where in the pandas project can it be found. Is it defined somewhere in the previous *.rst file. 

By writing `pd.offsets.Second(...)` it's basically clear on first glance. thanks @FHaase 

yeah more explicit the better.