-
Notifications
You must be signed in to change notification settings - Fork 54
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
Namespace cleanup #408
Namespace cleanup #408
Conversation
integrators, | ||
) | ||
from gpjax.base import ( | ||
Module, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably better to be consistent but gpjax.Module
(and perhaps the param_field
) is the one thing I would've just kept in the "top-level" namespace.
Edit: actually, Dataset
is in the top-level namespace as well so maybe that's an argument to keep Module, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolved in forthcoming commit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, and overall I'm very happy with these changes - though I would
- suggest (but not bother arguing about) keeping
Module
andparam_field
in the top-level name-space - strongly suggest (and be willing to argue) that this is breaking and bump the version to 0.8.0 to follow semantic versioning
- there's pending merge conflicts that I've not reviewed
Co-authored-by: st-- <[email protected]> Signed-off-by: Thomas Pinder <[email protected]>
…PJax into namespace_cleanup
Type of changes
Checklist
poetry run pre-commit run --all-files --show-diff-on-failure
before committing.Description
This PR cleans up the package's namespace, as per Slack discussions.
Issue Number: N/A