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

Decouple end user dependencies from development dependencies in pixi.toml #101

Closed
kklein opened this issue Feb 6, 2025 · 0 comments · Fixed by #102
Closed

Decouple end user dependencies from development dependencies in pixi.toml #101

kklein opened this issue Feb 6, 2025 · 0 comments · Fixed by #102

Comments

@kklein
Copy link
Collaborator

kklein commented Feb 6, 2025

Status quo

As of now, the dependencies section in pixi.toml looks as follows:

https://github.com/Quantco/metalearners/blob/main/pixi.toml#L13-L45

Notably, it includes dependencies, such as pytest, which are required for development of the metalearners library but not for its use by an end consumer.

This is plainly apparent when looking at the run requirements of metalearners' conda-forge recipe:

https://github.com/conda-forge/metalearners-feedstock/blob/main/recipe/meta.yaml#L24-L31

Objective

Separate development dependencies from end user dependencies in pixi.toml. This will make it

  • easier to keep the conda-forge recipe in a correct and consistent state and
  • more transparent if a code change imposes the burden of an additional dependency on the end user.
@kklein kklein changed the title Decouple client dependencies from development dependencies in pixi.toml Decouple end user dependencies from development dependencies in pixi.toml Feb 6, 2025
@kklein kklein linked a pull request Feb 11, 2025 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant