[ENH] export key objects at root #113
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Arrrghhhhh same test failure as per #114 |
|
@fkiraly I personally am not a fan of having things exportable from multiple public facing modules (e.g., skbase.base or skbase.lookup and also skbase). To me it creates ambiguity in expected usage by our (eventual) downstream users. |
|
alright then. Let's keep it as is if you feel that way - no too strong opinions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds exports at
skbaseroot level, forBaseObject,BaseMetaObject,BaseEstimator, andall_objects.Fixes #110
Of course it's worth discussing whether we want this, first (in #110)