Skip to content
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

DataFrame.unstack() issues DeprecationWarning with MultiIndex #11162

Closed
xflr6 opened this issue Sep 21, 2015 · 7 comments
Closed

DataFrame.unstack() issues DeprecationWarning with MultiIndex #11162

xflr6 opened this issue Sep 21, 2015 · 7 comments
Labels
Compat pandas objects compatability with Numpy or Python functions

Comments

@xflr6
Copy link
Contributor

xflr6 commented Sep 21, 2015

>>> import warnings
>>> warnings.simplefilter('error')

>>> import pandas as pd
>>> pd.__version__
u'0.17.0rc1'

>>> df = pd.DataFrame({'A': list('aabb'), 'B': [0, 1, 0, 1], 'C': range(4)})
>>> gf = df.groupby(['A', 'B']).sum()
>>> gf
     C
A B   
a 0  0
  1  1
b 0  2
  1  3

>>> gf.unstack()
Traceback (most recent call last):
..., line 4274, in _reference_duplicate_name
    return np.sum(name == np.asarray(self.names)) > 1
DeprecationWarning: elementwise == comparison failed; this will raise an error in the future.
@jreback
Copy link
Contributor

jreback commented Sep 21, 2015

what version numpy?

there are 'lots' of these. We do have to fix this at some point. But its not a big deal.

I can't actually repro your result.

@jreback jreback added the Compat pandas objects compatability with Numpy or Python functions label Sep 21, 2015
@jreback
Copy link
Contributor

jreback commented Sep 21, 2015

this is covered in #8537

pull-requests always welcome!

@jreback jreback closed this as completed Sep 21, 2015
@xflr6
Copy link
Contributor Author

xflr6 commented Sep 21, 2015

Yes, sorry, I just realized this seems to be due to this in the numpy 1.10.0b1 I am using here.

The line in the traceback seems to involve a comparison like: -1 == np.asarray(['A', 'B'])

@jreback
Copy link
Contributor

jreback commented Sep 21, 2015

We actually test with this: https://travis-ci.org/pydata/pandas/jobs/81396483
numpy master with DeprecationWarnings turned on. I try to get rid of them; I think I got most but their are some (also the 3.4 build has some as well).

so eventually have to fix!

@rosnfeld
Copy link
Contributor

Yup, I just hit this one today too when I did a fresh pull of the latest pandas and numpy.
Another repro case:

pd.DataFrame([[1, 2], [3, 4]], columns=['a', 'b']).groupby('a').b.value_counts().unstack()

@jreback
Copy link
Contributor

jreback commented Oct 14, 2015

yeh this is a numpy warning - never got around to tracking this one down

you are welcome to it!

@xflr6
Copy link
Contributor Author

xflr6 commented Oct 15, 2015

Maybe this should be re-opened (does #8537 mention mixed-type comparisons?).

I hope, we already tracked it: Wouldn't it be enough to replace this

return np.sum(name == np.asarray(self.names)) > 1

with this?

return sum(name == n for n in self.names) > 1

Dr-Irv added a commit to Dr-Irv/pandas that referenced this issue Oct 24, 2015
This includes updates to 3 Excel files, plus a test in test_excel.py,
plus the fix in parsers.py

issue when read_html with previous fix

With read_html, the fix didn't work on Python 2.7.  Handle the string
conversion correctly

Add bug fixed to what's new

Revert "Add bug fixed to what's new"

This reverts commit 05b2344.

Revert "issue when read_html with previous fix"

This reverts commit d1bc296.

Add what's new to describe bug.  fix issue with original fix

Added text to describe the bug.
Fixed issue so that it works correctly in Python 2.7

Add round trip test

Added round trip test and fixed error in writing sheets when
merge_cells=false and columns have multi index

DEPR: deprecate pandas.io.ga, pandas-dev#11308

DEPR: deprecate engine keyword from to_csv pandas-dev#11274

remove warnings from the tests for deprecation of engine in to_csv

PERF: Checking monotonic-ness before sorting on an index pandas-dev#11080

BUG: Bug in list-like indexing with a mixed-integer Index, pandas-dev#11320

Add hex color strings test

CLN: GH11271 move _get_handle, UTF encoders to io.common

TST: tests for list skiprows in read_excel

BUG: Fix to_dict() problem when using only datetime pandas-dev#11247

Fix a bug where to_dict() does not return Timestamp when there is only
datetime dtype present.

Undo change for when columns are multiindex

There is still something wrong here in the format of the file when there
are multiindex columns, but that's for another day

Fix formatting in test_excel and remove spurious test

See title

BUG: bug in comparisons vs tuples, pandas-dev#11339

bug#10442 : fix, adding note and test

BUG pandas-dev#10442(test) : Convert datetimelike index to strings with astype(str)

BUG#10422: note added

bug#10442 : tests added

bug#10442 : note udated

BUG pandas-dev#10442(test) : Convert datetimelike index to strings with astype(str)

bug#10442: fix, adding note and test

bug#10442: fix, adding note and test

Adjust test so that merge_cells=False works correctly

Adjust the test so that if merge_cells=false, it does a proper
formatting of the columns in the single row header, and puts the row
header in the first row

Fix test for Python 2.7 and 3.5

The test is failing on Python 2.7 and 3.5, which appears to read in the
values as floats, and I cannot replicate.  So force the tests to pass by
just making the column names equal when merge_cells=False

Fix for openpyxl < 2, and for issue pandas-dev#11408

If using openpyxl < 2, and value is a string that could be a number,
force a string to be written out.  If using openpyxl >= 2.2, then fix
issue pandas-dev#11408 to do with merging cells

Use set_value_explicit instead of set_explicit_value

set_value_explicit is in openpyxl 1.6, changed in openpyxl 1.8, but
there is code in 1.8 to set set_value_explicit to set_explicit_value for
compatibility

Add line in whatsnew for issue 11408

ENH: added capability to handle Path/LocalPath objects, pandas-dev#11033

DOC: typo in whatsnew/0.17.1.txt

PERF: Release GIL on some datetime ops

BUG: Bug in DataFrame.replace with a datetime64[ns, tz] and a non-compat to_replace pandas-dev#11326

CLN: clean up internal impl of fillna/replace, xref pandas-dev#11153

PERF: fast inf checking in to_excel

PERF: Series.dropna with non-nan dtypes

fixed pathlib tests on windows

DEPR: remove some SparsePanel deprecation warnings in testing

DEPR: avoid numpy comparison to None warnings

API: indexing with a null key will raise a TypeError rather than a ValueError, pandas-dev#11356

WARN: elementwise comparisons with index names, xref pandas-dev#11162

DEPR warning in io/data.py w.r.t. order->sort_values

WARN: more elementwise comparisons to object

WARN: more uncomparables of numeric array vs object

BUG: quick fix for pandas-dev#10989

TST: add test case from Issue pandas-dev#10989

API: add _to_safe_for_reshape to allow safe insert/append with embedded CategoricalIndexes

Signed-off-by: Jeff Reback <jeff@reback.net>

BLD: conda

Revert "BLD: conda"

This reverts commit 0c8a8e1.

TST: remove invalid symbol warnings

TST: move some tests to slow

TST: fix some warnings filters

TST: import pandas_datareader, use for tests

TST: remove some deprecation warnings from imports

DEPR: fix VisibleDeprecationWarnings in sparse

TST: remove some warnings in test_nanops

ENH: Improve the error message in to_gbq when the DataFrame schema does not match pandas-dev#11359

add libgfortran to 1.8.1 build

binstar -> anaconda

remove link to issue 11328 in whatsnew

Fixes to document issue in code, small efficiency fix

Try to resolve rebase conflict in whats new
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compat pandas objects compatability with Numpy or Python functions
Projects
None yet
Development

No branches or pull requests

3 participants