You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently one can specify dtype="category" to specify data as CategoricalDtype, and since it does not convey ordered information, we treat it as ordered=None internally in order to no-op data that is already categorical. Therefore internally, there are scenarios where we need to be mindful if we have ordered=None vs ordered=True/False
To simplify this gymnastics, it would be great if dtype="category" always meant CategoricalDtype(ordered=False). I think we would only need to issue a deprecation warning when specifying dtype="category" when the data is categorical and ordered=True
The text was updated successfully, but these errors were encountered:
Currently one can specify
dtype="category"
to specify data asCategoricalDtype
, and since it does not convey ordered information, we treat it asordered=None
internally in order to no-op data that is already categorical. Therefore internally, there are scenarios where we need to be mindful if we haveordered=None
vsordered=True/False
To simplify this gymnastics, it would be great if
dtype="category"
always meantCategoricalDtype(ordered=False)
. I think we would only need to issue a deprecation warning when specifyingdtype="category"
when the data is categorical andordered=True
The text was updated successfully, but these errors were encountered: