Whatsnew reorganization #24799
Whatsnew reorganization #24799
Conversation
| - :func:`pd.offsets.generate_range` argument ``time_rule`` has been removed; use ``offset`` instead (:issue:`24157`) | ||
| - In 0.23.x, pandas would raise a ``ValueError`` on a merge of a numeric column (e.g. ``int`` dtyped column) and an ``object`` dtyped column (:issue:`9780`). We have re-enabled the ability to merge ``object`` and other dtypes; pandas will still raise on a merge between a numeric and an ``object`` dtyped column that is composed only of strings (:issue:`21681`) | ||
|
|
||
| Percentage change on groupby |
There was a problem hiding this comment.
This section was collapsed into a single line in https://github.com/pandas-dev/pandas/pull/24799/files#diff-f7aa70fb13c1915d211d6a0257977262R1812. I don't think it's a backwards incompatible change.
| * :ref:`New APIs for accessing the array backing a Series or Index <whatsnew_0240.values_api>` | ||
| * :ref:`A new top-level method for creating arrays <whatsnew_0240.enhancements.array>` | ||
| * :ref:`Store Interval and Period data in a Series or DataFrame <whatsnew_0240.enhancements.interval>` | ||
| * :ref:`Support for joining on two MultiIndexes <whatsnew_0240.enhancements.join_with_two_multiindexes>` |
There was a problem hiding this comment.
Maybe also add something about the sparse changes?
Or something about the "general improvements of the ExtensionArray interface" (although that is maybe too advanced / niche for the average user)
There was a problem hiding this comment.
Highlight: If you were using SparseArrays we probably broke your code :)
I'm planning to go into much more detail about the extension array stuff in the blog post, so slightly inclined to not say too much here, as it's probably not directly relevant for the average user.
|
lgtm. after CI fixes are merge, let's repush and merge on green. |
Codecov Report
@@ Coverage Diff @@
## master #24799 +/- ##
==========================================
+ Coverage 42.92% 42.94% +0.02%
==========================================
Files 166 166
Lines 52382 52382
==========================================
+ Hits 22485 22498 +13
+ Misses 29897 29884 -13
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24799 +/- ##
===========================================
+ Coverage 42.92% 92.38% +49.46%
===========================================
Files 166 166
Lines 52382 52382
===========================================
+ Hits 22485 48395 +25910
+ Misses 29897 3987 -25910
Continue to review full report at Codecov.
|
|
Gonna just fix the merge conflict and merge if that's OK (other PR removed a section). |
|
|
||
| **Equality and Hashability** | ||
|
|
||
| Pandas now requires that extension dtypes be hashable. The base class implements |
There was a problem hiding this comment.
Seems I'm a bit too late to mention this on time. In #22476 (comment), we talked about this line.
How about: Pandas now requires that extension dtypes be hashable (i.e. the respective ExtensionDtype-objects; hashability is not a requirement for the values of the corresponding ExtensionArray).
|
Seems that comment about the hashable dtype we talked about hasn't made it into master yet. Just mentioning if you still wanna do that before release. |
|
Hmm keep forgetting to update it.
…On Wed, Jan 23, 2019 at 4:20 PM h-vetinari ***@***.***> wrote:
@TomAugspurger <https://github.com/TomAugspurger>
Seems that comment about the hashable dtype we talked about hasn't made it
into master yet. Just mentioning if you still wanna do that before release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24799 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIhX4vlicPDxAaymktc_QkTIWQAn6ks5vGOA7gaJpZM4aDDvt>
.
|
Changes
cc @jorisvandenbossche