-
-
Notifications
You must be signed in to change notification settings - Fork 374
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::pip
's 'latest' not compatible with latest 'pip' (version 20.3) due to changed output
#586
Comments
python::pip
's 'latest' not compatible with latest pip (version 20.3) due to change outputpython::pip
's 'latest' not compatible with latest 'pip' (version 20.3) due to change output
python::pip
's 'latest' not compatible with latest 'pip' (version 20.3) due to change outputpython::pip
's 'latest' not compatible with latest 'pip' (version 20.3) due to changed output
Hi, |
This test currently fails because of voxpupuli#586
This test currently fails because of voxpupuli#586
I managed to reproduce the error in #591 |
This test currently fails because of voxpupuli#586
There is a huge discussion on pypa/pip#9139 to bring functionality back, but for now, one can use
notice that you don't have to add anything after |
This test currently fails because of voxpupuli#586
This test currently fails because of voxpupuli#586
Hi, a resolution has since been proposed and merged to resolver pypa/pip#9139 by a contributor. Are there still things missing to resolve this? |
I have the latest pip 21.0.1 and feature is not included there yet |
Yes, the change will be the 21.1 release due this month. I was asking whether there are any more things you’d need, or maybe some people to test 21.1 against the current main branch to make sure it works for you, so we don’t need to wait for another feature release to get this resolved. |
should be fixed in newer version? pypa/pip#9405 |
pip did it again ... see #695 |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Starting with
20.3
pip is using a new dependency resolver which does not produce the same output as before and breaks puppet-python's logic to determine latest available package version.Upgrade to pip
20.3
and try installing latest of any package viapython::pip
.What are you seeing / What behaviour did you expect instead
With pip
20.2.4
installing a non-existing version returns all available versions (see below).Starting with version
20.3
this information is not returned anymore.relevant Puppet code
This snippet is from
pip.pp
and fails due to the missingfrom versions:
string that was dropped with the new dependecy resolver.reference
The text was updated successfully, but these errors were encountered: