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

Dependency resolution issue with Poetry #335

Closed
pawamoy opened this issue Apr 2, 2021 · 3 comments
Closed

Dependency resolution issue with Poetry #335

pawamoy opened this issue Apr 2, 2021 · 3 comments

Comments

@pawamoy
Copy link

pawamoy commented Apr 2, 2021

Just so you know, backports.entry-points-selectable specifies Python markers for its pytest-mypy dependency that are not being parsed correctly by Poetry, resulting in errors while resolving dependencies for pytest-randomly 3.6.0. See python-poetry/poetry#3862 (comment) and the previous comments. I'll temporarily pin pytest-randomly to 3.5.0 🙂

@pawamoy pawamoy closed this as completed Apr 2, 2021
@adamchainz
Copy link
Member

I suggest you also open an issue upstream in backports.entry-points-selectable. That's only a testing requirement so I don't see why poetry would even need to touch it if you didn't specify to install backports.entry-points-selectable[testing]

@pawamoy
Copy link
Author

pawamoy commented Apr 3, 2021

Yes I already did yesterday: jaraco/backports.entry_points_selectable#2 🙂

As for why Poetry reads these, I'm not knowledgeable enough in dependency resolution algorithms or Poetry itself to answer! 😄

@hukkin
Copy link
Contributor

hukkin commented Apr 11, 2021

I went ahead and opened a PR for this before realizing this closed issue existed.

I think specifying the dependencies as >= 3 makes more sense even if the Poetry issue is fixed. As far as I know >3 is equivalent to >=3 and !=3. Feels a bit strange to me to arbitrarily exclude Python version 3.0.0 (but not 3.0.1 for instance).

EDIT: Oops I thought I was in backports.entry-points-selectable issue tracker.... 🤦 Will post this there as well.

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