-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Move json_normalize to pd namespace #27586
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
Comments
I totally agree. |
I'd like to contribute to this patch. If I understand correctly, I'll have to import Are there any additional warnings (future / deprecation) that need to be added for this change? |
Start with that and a whatsnew. We may also want to throw a FutureWarning when someone tries importing from pandas.io.json; not sure best way to do that so can maybe just submit first part and we can discuss from there |
Is this needed? We have always consistently documented it to be imported from there (and we also have other public functionality in that submodule), so this just gives code churn for not much reason I think. Of course for There is also (see also the comment I made in #27522 about json_normalize being far from the only public non-top-level function, although it might be the most used one, I don't know) |
Is this still being worked on? If not I can pick it up! |
It is being worked on in #27615. |
This function I think gets a good amount of usage but people tend to import from
pandas.io.json
. ref #27522 I think we should move this to the top levelcc @bhavaniravi
The text was updated successfully, but these errors were encountered: