-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: clarify default behavior for categories ordering #22081
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #22081 +/- ##
=======================================
Coverage 92.07% 92.07%
=======================================
Files 170 170
Lines 50688 50688
=======================================
Hits 46671 46671
Misses 4017 4017
Continue to review full report at Codecov.
|
lgtm. @TomAugspurger @jorisvandenbossche wording look ok? |
pandas/core/arrays/categorical.py
Outdated
@@ -241,10 +241,14 @@ class Categorical(ExtensionArray, PandasObject): | |||
categories will be replaced with NaN. | |||
categories : Index-like (unique), optional | |||
The unique categories for this categorical. If not given, the | |||
categories are assumed to be the unique values of values. | |||
categories are assumed to be the unique values of values (sorted, if |
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.
The second values
should be in backticks.
ea68572
to
ddb03e4
Compare
git diff upstream/master -u -- "*.py" | flake8 --diff
Just a doc clarification on default categories ordering, which can be pretty confusing when handling mixed dtypes (see also #22080 ).