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.

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

Rethinking Zarr's core dependencies #2391

Open
jhamman opened this issue Oct 16, 2024 · 0 comments
Open

Rethinking Zarr's core dependencies #2391

jhamman opened this issue Oct 16, 2024 · 0 comments

Comments

@jhamman
Copy link
Member

jhamman commented Oct 16, 2024

I'd like to open the conversation about what Zarr's core dependencies are for 3.0. Currently, this looks like:

dependencies = [
'asciitree',
'numpy>=1.25',
'fasteners',
'numcodecs>=0.10.2',
'fsspec>2024',
'crc32c',
'typing_extensions',
'donfig',
]

Some of these are not used anymore (asciitree and fasteners) so those can safely go.

Then there is fsspec and crc32c. These are only needed for the RemoteStore and ShardingCodec, respectively. What do we think about making these optional?

One proposed diff in our dependencies would look something like:

 dependencies = [
-    'asciitree',
     'numpy>=1.25',
-    'fasteners',
-    'numcodecs>=0.10.2',
-    'fsspec>2024',
-    'crc32c',
+    'numcodecs>=0.12',
     'typing_extensions',
     'donfig',
 ]

 [project.optional-dependencies]
+remote = [
+    "fsspec",
+]
+sharding = [
+    "crc32c",
+]

Notes:

  • fsspec is pure python with no dependencies so is not a particular heavy dependency.
  • crc32c could potentially move into numcodecs, right?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant