DOC: small whatsnew updates #18219
DOC: small whatsnew updates #18219
Conversation
| - Better support for ``Dataframe.style.to_excel()`` output with the ``xlsxwriter`` engine. (:issue:`16149`) | ||
| - :func:`pd.tseries.frequencies.to_offset()` now accepts leading '+' signs e.g. '+1h'. (:issue:`18171`) | ||
| - Better support for :func:`Dataframe.style.to_excel` output with the ``xlsxwriter`` engine. (:issue:`16149`) | ||
| - :func:`pandas.tseries.frequencies.to_offset` now accepts leading '+' signs e.g. '+1h'. (:issue:`18171`) |
There was a problem hiding this comment.
@jorisvandenbossche @TomAugspurger I can't get this one to render, what is wrong here?
There was a problem hiding this comment.
Looks like to_offset isn't in api.rst. It would need an
.. autosummary:
:toctree: generated/
tseries.frequencies.to_offset
I think.
There was a problem hiding this comment.
ahh, and that's actually a pretty useful function, should prob be in pd namespace
| .. autosummary:: | ||
| :toctree: generated/ | ||
|
|
||
| DateOffset |
There was a problem hiding this comment.
these weren't anywhere :< (not the complete list as didn't put up businesss ones).....
doc/source/whatsnew/v0.22.0.txt
Outdated
| @@ -41,10 +41,10 @@ Other API Changes | |||
| ^^^^^^^^^^^^^^^^^ | |||
|
|
|||
| - ``NaT`` division with :class:`datetime.timedelta` will now return ``NaN`` instead of raising (:issue:`17876`) | |||
| - All-NaN levels in ``MultiIndex`` are now assigned float rather than object dtype, coherently with flat indexes (:issue:`17929`). | |||
| - All-NaN levels in a ``MultiIndex`` are now assigned ``float`` rather than ``object`` dtype, promoting consistency with ``Index`` (:issue:`17929`). | |||
| - :class:`Timestamp` will no longer silently ignore unused or invalid `tz` or `tzinfo` keyword arguments (:issue:`17690`) | |||
| - :class:`Timestamp` will no longer silently ignore invalid `freq` arguments (:issue:`5168`) | |||
There was a problem hiding this comment.
On the lines 45/46: tz, tzinfo, and freq should have two backticks instead of one.
|
this may not be exactly correct from a doc perspective (and prob adds some warnings), but getting the data in the right place for now. |
|
A bit late (could also keep such things open a bit longer), but:
|
|
right this was mainly to get things started |
No description provided.