-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Incorrect requirements.txt formatting in poetry export #12
Comments
pmav99
added a commit
to pmav99/poetry-export-plugin
that referenced
this issue
Sep 30, 2021
…m constraints Fixes python-poetry#12 Related to: - python-poetry/poetry#4575 - pypa/packaging#456
pmav99
added a commit
to pmav99/poetry
that referenced
this issue
Oct 2, 2021
2 tasks
pmav99
added a commit
to pmav99/poetry
that referenced
this issue
Nov 11, 2021
2 tasks
neersighted
pushed a commit
to python-poetry/poetry
that referenced
this issue
Nov 14, 2021
neersighted
pushed a commit
that referenced
this issue
Nov 14, 2021
…m constraints Fixes #12 Related to: - python-poetry/poetry#4575 - pypa/packaging#456
1nF0rmed
pushed a commit
to 1nF0rmed/poetry
that referenced
this issue
Nov 15, 2021
edvardm
pushed a commit
to edvardm/poetry
that referenced
this issue
Nov 24, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The
requirements.txt
format needs to put a space in front of the semicolon that specifies the package and the pyversion and platform constraints. Right now, without the space, the semicolon will be interpreted as part of a URL. See this issue in packaging:pypa/packaging#456
Related to:
python-poetry/poetry#4575
pypa/packaging#456
The text was updated successfully, but these errors were encountered: