On Tue, 2023-02-14 at 13:07 -0800, Stefan van der Walt wrote:
On Tue, Feb 14, 2023, at 12:27, Ralf Gommers wrote:
Okay, as long as we keep in mind that it should contain all these not-for-main-namespace functions/classes, it seems fine with me. We can live with two namespaces (`types` and `exceptions`), but more would get a bit too much. We were planning to use `np.lib.*` for more detailed user-facing functions that didn't belong in the main namespace, so let's make sure that we don't end up with >2 of these kinds of namespaces right below the top level one.
If it's mainly for internal use, we can also use sub-namespaces under lib right now, and not add those to the main namespace with the next release? I.e., we can create `lib.types`, `lib.exceptions` and whatever we want, and then import lib as _np or similar internally.
Do you (or anyone else) have a preference? Using `np.lib.<submodule>` for future things especially if they don't feel like core functionality seems good. (I am not a big fan of having a second large namespace, but have little preference for where we would would put new submodules, i.e. in `np.lib`.<submodule> or `np.<submodule>` directly.)
For these particular ones, I still slightly prefer `np.types` and `np.exceptions`, but happy either way. One disadvantage of the main namespace is that it is so large, it is hard to find submodules :).
Stéfan _______________________________________________ NumPy-Discussion mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: email@example.com