Uh oh!
There was an error while loading. Please reload this page.
[v3] reorganize package - move most modules to zarr.core - #2072
Conversation
Uh oh!
There was an error while loading. Please reload this page.
…nto feature/core-subpackage
dstansby
left a comment
There was a problem hiding this comment.
As a general comment, objects should only be listed in one all throughout the codebase. This should be where we are expecting users to import the object from. We are still free to import from other locations internally, but all signals where the public API lives.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jhamman
commented
Aug 12, 2024
@zarr-developers/python-core-devs - this is ready for a real review now. Thanks @dstansby and @normanrz for an initial look. With these changes, the package organization now looks like this: |
…nto feature/core-subpackage
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
d-v-b
commented
Aug 14, 2024
merging! thanks @jhamman |
* v3: [v3] reorganize package - move most modules to zarr.core (zarr-developers#2072)
This PR creates a
coresubpackage in the zarr package and begins to move some modules there. As I explained in #2037 (comment), this is designed to clarify which parts of the zarr project are public API and which are internal (everything incore).In my in my initial commit, I only moved
array.py,config.py,group.py,indexing.py, andsync.py. More to be done but I wanted to put this up for an initial reactions before going through the complete set of modules.closes#2037