scipy.org, as data

* Methods / functions / classes and module attributes whose names begin with aleading underscore are private.* If a class name begins with a leading underscore, none of its members arepublic, whether or not they begin with a leading underscore.* If a module name in a package begins with a leading underscore none ofits members are public, whether or not they begin with a leading underscore.* If a module or package defines `__all__`, that authoritatively defines the* If a module or package doesn’t define `__all__`, then all names that don’tstart with a leading underscore are public.Reading the above guidelines one could draw the conclusion that everyprivate module or object starts with an underscore. This is not thecase; the presence of underscores do mark something as private, butthe absence of underscores do not mark something as public.In SciPy there are modules whose names don’t start with an underscore, but thatshould be considered private. To clarify which modules these are, we definebelow what the public API is for SciPy, and give some recommendations for howto import modules/functions/objects from SciPy.## Guidelines for importing functions from SciPy#Everything in the namespaces of SciPy submodules is public. In general inPython, it is recommended to make use of namespaces. For example, thefunction `curve_fit` (defined in `scipy/optimize/_minpack_py.py`) should beresult = scipy.optimize.curve_fit(...)Or alternatively one could use the submodule as a namespace like so:For `scipy.io` prefer the use of `import scipy`because `io` is also the name of a module in the PythonIn some cases, the public API is one level deeper. For example, the`scipy.sparse.linalg` module is public, and the functions it contains are notavailable in the `scipy.sparse` namespace. Sometimes it may result in moreeasily understandable code if functions are imported from one level deeper.