-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
CategoricalAccessor.categorical removed in 0.24.0rc1 #24751
Comments
Will take a look at this one. |
I am not sure we need to deprecate this at all. This is a non-public interface to begin with (and not in-line with anything else in pandas). |
It wasn't prefixed with an underscore.
…On Sun, Jan 13, 2019 at 3:27 PM Jeff Reback ***@***.***> wrote:
I am not sure we need to deprecate this at all. This is a non-public
interface to begin with (and not in-line with anything else in pandas).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24751 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHItllU5Hi3G1qp2aeg4thfT1g_j5aks5vC6TSgaJpZM4Z9RPT>
.
|
lots of things are not prefixed with underscored. |
We made a mistake and the data was made public. We need a deprecation.
…________________________________
From: Jeff Reback <notifications@github.com>
Sent: Sunday, January 13, 2019 15:41
To: pandas-dev/pandas
Cc: Tom Augspurger; Author
Subject: Re: [pandas-dev/pandas] CategoricalAccessor.categorical removed in 0.24.0rc1 (#24751)
It wasn't prefixed with an underscore.
lots of things are not prefixed with underscored. .categoricals is not a valid construction, nor was this ever advertised / documented. This is taking deprecations too far.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#24751 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABQHIvgcgoLFPoKzmUIXvdkg3FG4PC6uks5vC6gBgaJpZM4Z9RPT>.
|
@TomAugspurger not convinced, we havemany places where you can access attributes; and we have changed any of these. This is a very very minor case. I don't think the deprecation is worth it. |
I think it is.
…________________________________
From: Jeff Reback <notifications@github.com>
Sent: Sunday, January 13, 2019 16:40
To: pandas-dev/pandas
Cc: Tom Augspurger; Mention
Subject: Re: [pandas-dev/pandas] CategoricalAccessor.categorical removed in 0.24.0rc1 (#24751)
@TomAugspurger<https://github.com/TomAugspurger> not convinced, we havemany places where you can access attributes; and we have changed any of these. This is a very very minor case. I don't think the deprecation is worth it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#24751 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABQHIhyuZsVVkfY0iztkFDhFMcX910-4ks5vC7XhgaJpZM4Z9RPT>.
|
It is very simple to deprecate it (it's not adding complexity to the non-deprecated code), so let's just do it. @benjaminr can you re-open your PR? |
@jorisvandenbossche sure thing 👍 |
…#24751 (pandas-dev#24754) * Implementation for CategoricalAccessor.categorical removed in 0.24.0rc1 pandas-dev#24751
…#24751 (pandas-dev#24754) * Implementation for CategoricalAccessor.categorical removed in 0.24.0rc1 pandas-dev#24751
Previously, CategoricalAccessor set
.categorical
in__init__
. I don't think this was intended to be the way to access things like.ordered
, but it wasn't prefixed with an underscore, so we should deprecate before removing0.23.4
0.24.0rc1
We can deprecate with
in
pandas/pandas/core/arrays/categorical.py
Line 2472 in 33f91d8
We should do the same for
.index
and.name
.The text was updated successfully, but these errors were encountered: