-
Notifications
You must be signed in to change notification settings - Fork 232
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
[Query] Dependency resolution failure across python versions #515
Comments
Thanks for the report. I could reproduce this with the Poetry prerelease ( # docker build --build-arg PYTHON_VERSION=3.7 --build-arg POETRY_VERSION=1.1.0b2 .
ARG PYTHON_VERSION
FROM python:$PYTHON_VERSION
ARG POETRY_VERSION
RUN curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python
ENV PATH $PATH:/root/.poetry/bin
RUN pip install cookiecutter
RUN cookiecutter gh:cjolowicz/cookiecutter-hypermodern-python --checkout="2020.8.15" --no-input
WORKDIR hypermodern-python
RUN poetry add rich
RUN poetry export -f requirements.txt | grep dataclasses | grep python_version There is already an upstream issue for this: python-poetry/poetry#2662 You can fix this by downgrading to the stable version of Poetry ( I'm closing this because it is an upstream bug. Feel free to comment and continue the discussion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
It appears that poetry's python specific package management doesn't translate properly to the export command Libraries for python3.6 are also getting exported which creating nox requirements for python3.7
Steps to reproduce
We get the following error:
The problem arrises due to dataclasses being exported in the requirements file for python3.7.
Even though the lock mentions that dataclasses should be installed only for python 3.6, why is that it gets exported for 3.7 ? Please let me know if I am missing something.
Thanks
The text was updated successfully, but these errors were encountered: