-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Relocate exceptions #14800 #15181
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
Relocate exceptions #14800 #15181
Conversation
…v#14761 Updating documentation to reflect change
DataFrame.astype now allows changing the dtype of a column by passing a dict mapping column name to dtype.
DataFrame.astype now allows setting the type of columns by passing a dict mapping column to dtype.
…com/m-charlton/pandas into update_docs_astype_with_dict_#14761
Mistakenly added changes carried out in v0.19 to v0.20
Move exceptions/warnings from pandas.core.common to pandas.api.exceptions The exceptions/warnings can still be imported from pandas.core.common however a DeprecationWarning will be issued when they are raised.
I think we had the same problem before (I seem to remember this from #14479), but decorating exceptions does not seem to work in practice:
|
O.K. Will wait further instructions. |
so I think what you have to do here, is add an option to IOW, we want to proxy So if you add an option (default it to True), to show the the |
closing in favor of #15541 |
git diff master | flake8 --diff
Deprecation warnings will only be issued when exceptions/warnings are raised. I did think of
putting a deprecation warning in
pandas.common.core
indicating that these exceptionswere deprecated but these would be seen when anything was imported from
pandas.core.common
. Please advise.