Skip to content

Use DeprecationWarning for core.common deprecations (GH13634) #13990

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

jorisvandenbossche
Copy link
Member

Related to second question in #13634 (whether to use FutureWarning or DeprecationWarning in deprecating the public pandas.core.common functions).

As those functions are mostly used in library code, and less directly by users in their own code, I think a DeprecationWarning is more appropriate in this case.
For example, in our own docs, we started to get warnings due to an example with a statsmodels regression that uses patsy using one of those functions. Note that recent IPython also shows DeprecationWarnings when using a deprecated function interactively.

@jorisvandenbossche jorisvandenbossche added this to the 0.19.0 milestone Aug 13, 2016
@jorisvandenbossche jorisvandenbossche added Deprecate Functionality to remove in pandas Clean labels Aug 13, 2016
@jreback
Copy link
Contributor

jreback commented Aug 13, 2016

lgtm

@codecov-io
Copy link

codecov-io commented Aug 13, 2016

Current coverage is 85.28% (diff: 100%)

Merging #13990 into master will not change coverage

@@             master     #13990   diff @@
==========================================
  Files           139        139          
  Lines         50206      50206          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits          42818      42818          
  Misses         7388       7388          
  Partials          0          0          

Powered by Codecov. Last update 29d9e24...2de5d48

@jreback jreback closed this in 0975509 Aug 13, 2016
@jreback
Copy link
Contributor

jreback commented Aug 13, 2016

thanks @jorisvandenbossche

I made a slight doc update.

@jorisvandenbossche
Copy link
Member Author

Thanks!

@jorisvandenbossche jorisvandenbossche deleted the common-depr-warning branch August 13, 2016 22:28
@jreback jreback mentioned this pull request Sep 30, 2016
TomAugspurger added a commit to TomAugspurger/pandas that referenced this pull request Jan 18, 2018
I have a PR incoming that would introduce a circular dependency
between pandas.core.arrays.categorical, pandas.api, and pandas.core.common.

This change will allow that PR to avoid hacky workarounds, since the
real problem is pandas.core importing pandas.api.types.

xref pandas-dev#13990
jreback added a commit to jreback/pandas that referenced this pull request Feb 19, 2018
jreback added a commit to jreback/pandas that referenced this pull request Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Clean Deprecate Functionality to remove in pandas
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants