-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DEPR: correct locations to access public json/parser objects in depr message #15909
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
Codecov Report
@@ Coverage Diff @@
## master #15909 +/- ##
==========================================
+ Coverage 90.95% 90.96% +<.01%
==========================================
Files 145 145
Lines 49535 49535
==========================================
+ Hits 45057 45058 +1
+ Misses 4478 4477 -1
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #15909 +/- ##
=========================================
Coverage ? 90.96%
=========================================
Files ? 145
Lines ? 49475
Branches ? 0
=========================================
Hits ? 45007
Misses ? 4468
Partials ? 0
Continue to review full report at Codecov.
|
hmm, I don't remember why I added compat for this. let me have a look. |
49d032b
to
77a8f2f
Compare
yeah I think we should just remove |
I don't know why you would need |
77a8f2f
to
f3f1c70
Compare
Added removal of |
@@ -60,11 +60,15 @@ | |||
# extension module deprecations | |||
from pandas.util.depr_module import _DeprecatedModule | |||
|
|||
json = _DeprecatedModule(deprmod='pandas.json', deprmodto='pandas.io.json.libjson') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you might be able to remove the deprmodto
argument entirely (which I added to handle moving modules).
Makes sense to me. Hopefully it doesn't break any tests. |
@gfyoung to be clear, it is not removed internally, only the public exposure is deprecated. So it is about whether external users would want to use it |
Yes, absolutely! I meant that hopefully no tests were accessing this variable externally. |
ok, used the script to rebase you locally and push up. seemed to work. |
thanks! |
Great! |
Another one remaining is
pd.parser.na_values
I don't think we should refer to
libparsers
, but for now it is not imported inpandas.io.parsers
as alternative. I could add it there, but the question is maybe whether this is actually useful for users? Maybe we should say that it will be removed without giving alternative?