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

Support project-specific dep overrides / settings in pyproject.toml #115

Open
mdekstrand opened this issue Oct 25, 2021 · 5 comments
Open

Comments

@mdekstrand
Copy link

mdekstrand commented Oct 25, 2021

It would be useful for conda-lock's pyproject.toml support if it could support configuring dependency-specific information directly in pyproject.toml. I see at least two things that would be useful to configure:

  • A dependency needs to be installed by Pip; this will probably only work with -k env, but would add the dependency to a pip section.
  • The Conda package name for a dependency (in case something isn't in the global rename file, or to remove dependency on it)

This could look something like:

[tool.cargo-lock.dependencies]
hpfrec = { source = "pip" }
msgpack = { conda-package = "python-msgpack" }
@mariusvniekerk
Copy link
Collaborator

mariusvniekerk commented Oct 25, 2021

This is conda-lock not cargo-lock?

@mdekstrand
Copy link
Author

@mariusvniekerk Oops, sorry. Meant conda-lock and "Conda package" - using both Conda & Cargo on different projects, brain slipped.

@mariusvniekerk
Copy link
Collaborator

Okay, that sounds reasonable to me. Changes would probably be needed mostly in the source parser and maybe the spec handler class to carry along the pip dependencies.

@olivier-lacroix
Copy link
Contributor

Being able to specify which packages should be installed via pip would indeed be great.

My understanding is that it is possible for poetry users currently, but that users of PEP621 pyproject.toml are unfortunately out of luck.

@olivier-lacroix
Copy link
Contributor

I have given it a go in #186 (for the pip item only)

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

3 participants