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

convert poetry sources to pip --index-url #12

Open
sanzoghenzo opened this issue Nov 2, 2020 · 0 comments · May be fixed by #13
Open

convert poetry sources to pip --index-url #12

sanzoghenzo opened this issue Nov 2, 2020 · 0 comments · May be fixed by #13

Comments

@sanzoghenzo
Copy link

Hi, first of all many thanks for this project!

TL;DR: the generated pip section should include the --index-url and --extra-index-url using info from tool.poetry.source

I'm on a limbo of mixed environments and repos, but I need to switch back from a poetry-based to a conda-based build env.
I already have some projects built with poetry and saved on a private devpi index;
the directive to use the private repo is in pyproject.toml's tool.poetry.source:

[[tool.poetry.source]]
name = "private"
url = "https://my.private.repo/my/stable/+simple/"
default= true

I added the tool.poetry2conda.dependencies section to mark my packages with channel = "pip", and when I use poetry2conda pyproject.toml environment.yml, the yaml file contains the pip packages but no --index-url option.

Passing extra options in the environment.yml's pip section is possible from conda version 4.4.0 (see this pr).

It would be wonderful if the urls specified in the tool.poetry.source sections could be translated to a --index-url entry if default = true, or a --extra-index-url otherwhise.

sanzoghenzo pushed a commit to sanzoghenzo/poetry2conda that referenced this issue Nov 2, 2020
@sanzoghenzo sanzoghenzo linked a pull request Nov 2, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant