-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Python] Doesn't handle well poetry dependencies depending on Python version #2503
Comments
Dependabot has also recently started failing with
on one of my repos too ( https://github.com/chris48s/mark-sideways ), although it is caused by effectively the same condition in one of my transitive dependencies: https://github.com/willmcgugan/rich/blob/a424fafc5654346b5d6e2db28ad19aad10040581/pyproject.toml#L27 I guess this is a manifestation of python-poetry/poetry#2386 as opposed to a bug in dependabot itself. Strangely, I'm unable to reproduce this locally with python 3.8/poetry 1.0.10 (although the last post in that linked issue says this is still an issue in that build, apparently) What version of poetry does dependabot use? (I don't think the error log on my repo tells me) |
We're currently on Poetry 1.0.10, and I'm in the process of upgrading to to 1.1.1 @chris48s |
Hopefully that upgrade will resolve it 🤞 |
I've now had a successful dependabot run on that repo |
Happy to hear it! Let's keep this open for a bit longer to make sure it's really resolved, please let me know if you spot anything weird |
It seems to be also working for me. |
Awesome! Alright I'm going to close this out for now, feel free to re-open if needed. |
Package manager/ecosystem
Python Poetry.
https://github.com/alexpdp7/caw/blob/master/pyproject.toml#L14
My project supports Python 3.6, 3.7 and 3.8, hence:
The project uses dataclasses, so on 3.6 I install a backport:
I think this worked OK, but recently Dependabot started spamming me with issues:
alexpdp7/caw#41
, which seem to complain about this issue.
The text was updated successfully, but these errors were encountered: