Skip to content

DataFrame with one column, which is categorical: single rows convert to scalars #14011

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

Closed
ChickenProp opened this issue Aug 16, 2016 · 2 comments · Fixed by #29521
Closed

DataFrame with one column, which is categorical: single rows convert to scalars #14011

ChickenProp opened this issue Aug 16, 2016 · 2 comments · Fixed by #29521
Labels
good first issue Needs Tests Unit test(s) needed to prevent regressions
Milestone

Comments

@ChickenProp
Copy link

Code Sample, a copy-pastable example if possible

In [2]: pd.DataFrame({'x': pd.Categorical('a b c d e'.split())}).iloc[0]
Out[2]: 'a'

Expected Output

I think this should be a Series with one element:

0    a
dtype: category
Categories (5, object): [a, b, c, d, e]

by analogy with the non-Categorical case:

In [3]: pd.DataFrame({'x': 'a b c d e'.split()}).iloc[0]
Out[3]:
x    a
Name: 0, dtype: object

This bug also exhibits with .loc[0] and .ix[0]. It doesn't happen if the original dataframe has more than one column, even if they're all categorical.

output of pd.show_versions()

INSTALLED VERSIONS

commit: None
python: 2.7.11.final.0
python-bits: 64
OS: Darwin
OS-release: 15.5.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_GB.UTF-8

pandas: 0.18.1
nose: 1.3.7
pip: 8.1.2
setuptools: 18.5
Cython: 0.23.4
numpy: 1.11.1
scipy: 0.18.0
statsmodels: 0.6.1
xarray: None
IPython: 4.0.1
sphinx: 1.3.1
patsy: 0.4.1
dateutil: 2.5.3
pytz: 2016.6.1
blosc: None
bottleneck: 1.0.0
tables: 3.2.2
numexpr: 2.6.0
matplotlib: 1.5.1
openpyxl: 2.2.6
xlrd: 0.9.4
xlwt: 1.0.0
xlsxwriter: 0.7.7
lxml: 3.4.4
bs4: 4.4.1
html5lib: None
httplib2: None
apiclient: None
sqlalchemy: 1.0.9
pymysql: None
psycopg2: None
jinja2: 2.8
boto: 2.40.0
pandas_datareader: None

ChickenProp added a commit to ChickenProp/ggplot that referenced this issue Aug 17, 2016
There's a bug where you get an error if you facet a geom_bar with a
single facet variable which is Categorical. This is an old bug, but
it's more visible now that there's a reason to use Categorical facet
variables. I think it's due to a bug in pandas:
pandas-dev/pandas#14011
@mroeschke mroeschke added Bug Indexing Related to indexing on series/frames, not to indexes themselves Categorical Categorical Data Type labels Oct 21, 2018
@mroeschke
Copy link
Member

This looks to work on master. Could use a test.

In [112]: In [2]: pd.DataFrame({'x': pd.Categorical('a b c d e'.split())}).iloc[0]
     ...:
Out[112]:
x    a
Name: 0, dtype: category
Categories (5, object): [a, b, c, d, e]

In [113]: pd.__version__
Out[113]: '0.26.0.dev0+652.g30362ed82'

@mroeschke mroeschke added good first issue Needs Tests Unit test(s) needed to prevent regressions and removed Bug Categorical Categorical Data Type Indexing Related to indexing on series/frames, not to indexes themselves labels Oct 23, 2019
@ryankarlos
Copy link
Contributor

@mroeschke had a go at this

@gfyoung gfyoung added this to the 1.0 milestone Nov 10, 2019
Reksbril pushed a commit to Reksbril/pandas that referenced this issue Nov 18, 2019
proost pushed a commit to proost/pandas that referenced this issue Dec 19, 2019
proost pushed a commit to proost/pandas that referenced this issue Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Needs Tests Unit test(s) needed to prevent regressions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants