Bootstrap v3 branch with zarrita

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'

[jhamman]

This PR begins taking steps toward the design described in #1583 and is intended to bootstrap the v3 development branch (note that this PR does not point at main). There is a lot more to do here but this felt like a decent starting point.

This branch is not yet wired up to the test suite so coverage, documentation checks are all expected to fail.

At this point, I've specifically taken the following steps:

1. Copied Zarrita at scalableminds/zarrita@7827478 into the v3 directory
2. applied Zarr-Python's linter rules
3. renamed zarrita -> v3
4. Added some (but not all) ABCs
5. Begin to incorporate these ABCs, mostly in the Array classes.

Pending some feedback from @normanrz and @d-v-b, my proposal is that we move to merge this into the v3 branch without much more work here. From there, we can start peeling small bits off of the design mentioned above.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[pep8speaks]

Hello @jhamman! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file zarr/v3/sharding.py:

Line 100:87: E203 whitespace before ':'
Line 114:48: E203 whitespace before ':'