-
Notifications
You must be signed in to change notification settings - Fork 141
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
Symbol hierarchy and reorganization #906
Comments
Worth thinking about. I do worry about difficult-to-categorize functions, though. In the modern world I've moved to "flatter" organizations but that usually is because of a search ability. I wonder if we need to improve discoverability of methods by other mechanisms? |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, a lot of symbols are directly reexported by its sub-packages without much organization, and that contributes to the long list of exported symbols:
Organizing these in a hierarchical and meaningful way is definitely a thing that we need to do for the 1.0 release.
I don't have a detailed proposal right now, but the basic idea is to introduce several submodules and organize them in a way like how
scikit-image
does:The text was updated successfully, but these errors were encountered: