In xref #13147
established a bit of a public api in pandas.api; ATM this only contains the type introspection routines.
Some disagreement on whether we should not do this, and rather just expose pandas.types directly.
I think pandas.api is actually very important because:
limits scope of what we choose to expose in the future; its not simply 'everything' that isnt nailed down (the case now). This does change pandas to make everything by default private, EXCEPT what is explicitly public.
a single entry point for other packages to use the pandas public API that is known / stable / maintained (will with c-API as well)
provide consistent naming externally (and allow us to fix / hide internally as needed)
namespaced. I only import what I need as a user / other package, rather than everything
as discussed here, should these deprecated API functions should be DeprecationWrarning rather than FutureWarning?
-> done in #13990
Ideally we should resolve this before the end of 0.19.0 (or remove it).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4