@@ -13,13 +13,13 @@ users upgrade to this version.
13
13
14
14
Highlights include:
15
15
16
- - Release the Global Interpreter Lock (GIL) on some cython operations, see :ref:`here <whatsnew_0170.gil>`
17
- - The default for ``to_datetime`` will now be to ``raise`` when presented with unparseable formats,
18
- previously this would return the original input, see :ref:`here <whatsnew_0170.api_breaking.to_datetime>`
19
- - The default for ``dropna`` in ``HDFStore`` has changed to ``False``, to store by default all rows even
20
- if they are all ``NaN``, see :ref:`here <whatsnew_0170.api_breaking.hdf_dropna>`
21
- - Support for ``Series.dt.strftime`` to generate formatted strings for datetime-likes, see :ref:`here <whatsnew_0170.strftime>`
22
- - Development installed versions of pandas will now have ``PEP440`` compliant version strings (:issue:`9518`)
16
+ - Release the Global Interpreter Lock (GIL) on some cython operations, see :ref:`here <whatsnew_0170.gil>`
17
+ - The default for ``to_datetime`` will now be to ``raise`` when presented with unparseable formats,
18
+ previously this would return the original input, see :ref:`here <whatsnew_0170.api_breaking.to_datetime>`
19
+ - The default for ``dropna`` in ``HDFStore`` has changed to ``False``, to store by default all rows even
20
+ if they are all ``NaN``, see :ref:`here <whatsnew_0170.api_breaking.hdf_dropna>`
21
+ - Support for ``Series.dt.strftime`` to generate formatted strings for datetime-likes, see :ref:`here <whatsnew_0170.strftime>`
22
+ - Development installed versions of pandas will now have ``PEP440`` compliant version strings (:issue:`9518`)
23
23
24
24
Check the :ref:`API Changes <whatsnew_0170.api>` and :ref:`deprecations <whatsnew_0170.deprecations>` before updating.
25
25
@@ -448,6 +448,7 @@ from ``7``.
448
448
449
449
.. ipython:: python
450
450
:suppress:
451
+
451
452
pd.set_option('display.precision', 6)
452
453
453
454
@@ -481,9 +482,9 @@ Series with a ``CategoricalIndex`` (:issue:`10704`)
481
482
- ``groupby`` using ``Categorical`` follows the same rule as ``Categorical.unique`` described above (:issue:`10508`)
482
483
- ``NaT``'s methods now either raise ``ValueError``, or return ``np.nan`` or ``NaT`` (:issue:`9513`)
483
484
484
- =============================== ==============================================================
485
+ =============================== ===============================================================
485
486
Behavior Methods
486
- =============================== ==============================================================
487
+ =============================== ===============================================================
487
488
``return np.nan`` ``weekday``, ``isoweekday``
488
489
``return NaT`` ``date``, ``now``, ``replace``, ``to_datetime``, ``today``
489
490
``return np.datetime64('NaT')`` ``to_datetime64`` (unchanged)
0 commit comments