-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
DOC: Fix heading capitalization in doc/source/whatsnew - part5 (#32550) #33568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 7 commits
ad2bd0c
aff897f
b393b54
d17f46e
3751c83
26ccbda
7953907
f9b39cc
0291e25
b095965
916e7dd
b2b5dfa
d879349
67cd736
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
.. _whatsnew_0181: | ||
|
||
v0.18.1 (May 3, 2016) | ||
--------------------- | ||
Version 0.18.1 (May 3, 2016) | ||
---------------------------- | ||
|
||
{{ header }} | ||
|
||
|
@@ -61,8 +61,8 @@ Tuesday after MLK Day (Monday is skipped because it's a holiday) | |
|
||
.. _whatsnew_0181.deferred_ops: | ||
|
||
``.groupby(..)`` syntax with window and resample operations | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``.GroupBy(..)`` syntax with window and resample operations | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
``.groupby(...)`` has been enhanced to provide convenient syntax when working with ``.rolling(..)``, ``.expanding(..)`` and ``.resample(..)`` per group, see (:issue:`12486`, :issue:`12738`). | ||
|
||
|
@@ -111,7 +111,7 @@ Now you can do: | |
.. _whatsnew_0181.enhancements.method_chain: | ||
|
||
Method chaining improvements | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The following methods / indexers now accept a ``callable``. It is intended to make | ||
these more useful in method chains, see the :ref:`documentation <indexing.callable>`. | ||
|
@@ -121,8 +121,8 @@ these more useful in method chains, see the :ref:`documentation <indexing.callab | |
- ``.loc[]``, ``iloc[]`` and ``.ix[]`` | ||
- ``[]`` indexing | ||
|
||
``.where()`` and ``.mask()`` | ||
"""""""""""""""""""""""""""" | ||
Methods ``.where()`` and ``.mask()`` | ||
"""""""""""""""""""""""""""""""""""" | ||
|
||
These can accept a callable for the condition and ``other`` | ||
arguments. | ||
|
@@ -134,8 +134,8 @@ arguments. | |
'C': [7, 8, 9]}) | ||
df.where(lambda x: x > 4, lambda x: x + 10) | ||
|
||
``.loc[]``, ``.iloc[]``, ``.ix[]`` | ||
"""""""""""""""""""""""""""""""""" | ||
Methods ``.loc[]``, ``.iloc[]``, ``.ix[]`` | ||
"""""""""""""""""""""""""""""""""""""""""" | ||
|
||
These can accept a callable, and a tuple of callable as a slicer. The callable | ||
can return a valid boolean indexer or anything which is valid for these indexer's input. | ||
|
@@ -148,8 +148,8 @@ can return a valid boolean indexer or anything which is valid for these indexer' | |
# callable returns list of labels | ||
df.loc[lambda x: [1, 2], lambda x: ['A', 'B']] | ||
|
||
``[]`` indexing | ||
""""""""""""""" | ||
Indexing with``[]`` | ||
""""""""""""""""""" | ||
|
||
Finally, you can use a callable in ``[]`` indexing of Series, DataFrame and Panel. | ||
The callable must return a valid input for ``[]`` indexing depending on its | ||
|
@@ -171,7 +171,7 @@ without using temporary variable. | |
|
||
.. _whatsnew_0181.partial_string_indexing: | ||
|
||
Partial string indexing on ``DateTimeIndex`` when part of a ``MultiIndex`` | ||
Partial string indexing on ``DatetimeIndex`` when part of a ``MultiIndex`` | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Partial string indexing now matches on ``DateTimeIndex`` when part of a ``MultiIndex`` (:issue:`10331`) | ||
|
@@ -306,8 +306,8 @@ API changes | |
|
||
.. _whatsnew_0181.api.groubynth: | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same here |
||
``.groupby(..).nth()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``.GroupBy(..).nth()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The index in ``.groupby(..).nth()`` output is now more consistent when the ``as_index`` argument is passed (:issue:`11039`): | ||
|
||
|
@@ -414,7 +414,7 @@ New behaviour: | |
|
||
.. _whatsnew_0181.apply_resample: | ||
|
||
Using ``.apply`` on groupby resampling | ||
Using ``.apply`` on GroupBy resampling | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Using ``apply`` on resampling groupby operations (using a ``pd.TimeGrouper``) now has the same output types as similar ``apply`` calls on other groupby operations. (:issue:`11742`). | ||
|
@@ -513,8 +513,8 @@ In addition to this error change, several others have been made as well: | |
|
||
.. _whatsnew_0181.api.to_datetime: | ||
|
||
``to_datetime`` error changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``to_datetime`` error changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Bugs in ``pd.to_datetime()`` when passing a ``unit`` with convertible entries and ``errors='coerce'`` or non-convertible with ``errors='ignore'``. Furthermore, an ``OutOfBoundsDateime`` exception will be raised when an out-of-range value is encountered for that unit when ``errors='raise'``. (:issue:`11758`, :issue:`13052`, :issue:`13059`) | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
.. _whatsnew_0190: | ||
|
||
v0.19.0 (October 2, 2016) | ||
------------------------- | ||
Version 0.19.0 (October 2, 2016) | ||
-------------------------------- | ||
|
||
{{ header }} | ||
|
||
|
@@ -37,8 +37,8 @@ New features | |
|
||
.. _whatsnew_0190.enhancements.asof_merge: | ||
|
||
``merge_asof`` for asof-style time-series joining | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Function ``merge_asof`` for asof-style time-Series joining | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do you mind restoring series here? This one is not referring to the class |
||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
A long-time requested feature has been added through the :func:`merge_asof` function, to | ||
support asof style joining of time-series (:issue:`1870`, :issue:`13695`, :issue:`13709`, :issue:`13902`). Full documentation is | ||
|
@@ -127,8 +127,8 @@ passed DataFrame (``trades`` in this case), with the fields of the ``quotes`` me | |
|
||
.. _whatsnew_0190.enhancements.rolling_ts: | ||
|
||
``.rolling()`` is now time-series aware | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``.rolling()`` is now time-Series aware | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same |
||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
``.rolling()`` objects are now time-series aware and can accept a time-series offset (or convertible) for the ``window`` argument (:issue:`13327`, :issue:`12995`). | ||
See the full documentation :ref:`here <stats.moments.ts>`. | ||
|
@@ -186,8 +186,8 @@ default of the index) in a DataFrame. | |
|
||
.. _whatsnew_0190.enhancements.read_csv_dupe_col_names_support: | ||
|
||
``read_csv`` has improved support for duplicate column names | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``read_csv`` has improved support for duplicate column names | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
.. ipython:: python | ||
:suppress: | ||
|
@@ -225,8 +225,8 @@ contained the values ``[0, 3]``. | |
|
||
.. _whatsnew_0190.enhancements.read_csv_categorical: | ||
|
||
``read_csv`` supports parsing ``Categorical`` directly | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``read_csv`` supports parsing ``Categorical`` directly | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The :func:`read_csv` function now supports parsing a ``Categorical`` column when | ||
specified as a dtype (:issue:`10153`). Depending on the structure of the data, | ||
|
@@ -394,8 +394,8 @@ After upgrading pandas, you may see *new* ``RuntimeWarnings`` being issued from | |
|
||
.. _whatsnew_0190.get_dummies_dtypes: | ||
|
||
``get_dummies`` now returns integer dtypes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``get_dummies`` now returns integer dtypes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The ``pd.get_dummies`` function now returns dummy-encoded columns as small integers, rather than floats (:issue:`8725`). This should provide an improved memory footprint. | ||
|
||
|
@@ -731,8 +731,8 @@ A ``Series`` will now correctly promote its dtype for assignment with incompat v | |
|
||
.. _whatsnew_0190.api.to_datetime_coerce: | ||
|
||
``.to_datetime()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Function ``.to_datetime()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Previously if ``.to_datetime()`` encountered mixed integers/floats and strings, but no datetimes with ``errors='coerce'`` it would convert all to ``NaT``. | ||
|
||
|
@@ -809,8 +809,8 @@ resulting dtype will be upcast, which is unchanged from previous. | |
|
||
.. _whatsnew_0190.api.describe: | ||
|
||
``.describe()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^ | ||
Method ``.describe()`` changes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Percentile identifiers in the index of a ``.describe()`` output will now be rounded to the least precision that keeps them distinct (:issue:`13104`) | ||
|
||
|
@@ -863,8 +863,8 @@ Furthermore: | |
``Period`` changes | ||
^^^^^^^^^^^^^^^^^^ | ||
|
||
``PeriodIndex`` now has ``period`` dtype | ||
"""""""""""""""""""""""""""""""""""""""" | ||
The ``PeriodIndex`` now has ``Period`` dtype | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think period is another one that will have to allow both period and Period. Can you use period lower case here please? |
||
"""""""""""""""""""""""""""""""""""""""""""" | ||
|
||
``PeriodIndex`` now has its own ``period`` dtype. The ``period`` dtype is a | ||
pandas extension dtype like ``category`` or the :ref:`timezone aware dtype <timeseries.timezone_series>` (``datetime64[ns, tz]``) (:issue:`13941`). | ||
|
@@ -1078,7 +1078,7 @@ Previously, most ``Index`` classes returned ``np.ndarray``, and ``DatetimeIndex` | |
|
||
.. _whatsnew_0190.api.multiindex: | ||
|
||
``MultiIndex`` constructors, ``groupby`` and ``set_index`` preserve categorical dtypes | ||
``MultiIndex`` constructors, ``GroupBy`` and ``set_index`` preserve Categorical dtypes | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
``MultiIndex.from_arrays`` and ``MultiIndex.from_product`` will now preserve categorical dtype | ||
|
@@ -1151,8 +1151,8 @@ As a consequence, ``groupby`` and ``set_index`` also preserve categorical dtypes | |
|
||
.. _whatsnew_0190.api.autogenerated_chunksize_index: | ||
|
||
``read_csv`` will progressively enumerate chunks | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
Function ``read_csv`` will progressively enumerate chunks | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
When :func:`read_csv` is called with ``chunksize=n`` and without specifying an index, | ||
each chunk used to have an independently generated index from ``0`` to ``n-1``. | ||
|
@@ -1190,8 +1190,8 @@ Sparse changes | |
|
||
These changes allow pandas to handle sparse data with more dtypes, and for work to make a smoother experience with data handling. | ||
|
||
``int64`` and ``bool`` support enhancements | ||
""""""""""""""""""""""""""""""""""""""""""" | ||
Types ``int64`` and ``bool`` support enhancements | ||
""""""""""""""""""""""""""""""""""""""""""""""""" | ||
|
||
Sparse data structures now gained enhanced support of ``int64`` and ``bool`` ``dtype`` (:issue:`667`, :issue:`13849`). | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If referring to the method should stick with
.groupby
The class can be capitalizedThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok but we need to change the algorithm in validate_rst_title_capitalization, because at the moment, every word 'groupby' will be seen as an exception, and needed to be capitalised like 'GroupBy'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you leave these
.groupby
methods in lower case. Not sure what's the best solution here, it needs to beGroupBy
when it's a class, andgroupby
when it's a method. And making the script be happy with both is not trivial, the way it is implemented.So, let's leave them correct for now, even if we can't add the validation to this file, and see what we do with the script. If you can open an issue for this case, that would be great. You can tag me on the issue. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I will switch back to
.groupby
and I will open an issue! And try to propose a solution when I can spend some time on it.