Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove undesired top-level imports before/with v2.0 #616

Open
mih opened this issue Feb 5, 2024 · 0 comments
Open

Remove undesired top-level imports before/with v2.0 #616

mih opened this issue Feb 5, 2024 · 0 comments
Milestone
2.0

Comments

@mih
Copy link
Member

mih commented Feb 5, 2024 •
edited
Loading

Here is an example PR #615

Look for markers in top-level __init__.py, such as # TODO REMOVE EVERTHING BELOW FOR V2.0 and act on them.

This will resolve #613 (might be closed before).

It would make sense to do a full run across all top-level __init__.py files, and try to slim the public API as much as possible when making breaking changes anyways.
@mih mih added this to the 2.0 milestone Feb 5, 2024
mih added a commit to mih/datalad-next that referenced this issue Feb 6, 2024
@mih
Uplift Python API docs
985cc94 
This continues the work done for datalad#613. Now all relevant symbols
are directly documented, for every top-level package.

In doing so, I added a first set of markers to shape the API
streamlining that will come with v2.0.
Ping datalad#624
Ping datalad#616

Some implementations that continued to be located in `__init__.py`
files have been move into new, dedicated source files.
@mih mih mentioned this issue Feb 6, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
1 participant
@mih