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

copy zarr-python dev environment #697

Open
d-v-b opened this issue Feb 6, 2025 · 2 comments
Open

copy zarr-python dev environment #697

d-v-b opened this issue Feb 6, 2025 · 2 comments

Comments

@d-v-b
Copy link
Contributor

d-v-b commented Feb 6, 2025

over in zarr-python, we have been pretty happy with our dev environment. I am wondering if we should bring those benefits over to numcodecs. Specifically, we would make the following changes:

  • use hatch for packaging
  • use the same linting / pre-commit configuration as zarr-python
  • use a src/numcodecs layout instead of numcodecs

Does anyone object to this proposal? I think it will generally improve the dev experience.

@martindurant
Copy link
Member

I bet no one objects if you are willing to put in the effort! numcodecs needs some more complex build, though, right?

it will generally improve the dev experience

Curious, do you have something specific in mind?

@d-v-b
Copy link
Contributor Author

d-v-b commented Feb 6, 2025

I'm mostly thinking of the hatch features we use over in zarr-python, like the option to run tests parametrized over python versions, environment-specific commands (e.g., for building docs), etc

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

2 participants