-
Notifications
You must be signed in to change notification settings - Fork 22
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
Updated version not detected #23
Comments
I noticed a similar behaviour with odoo modules. |
By default, pur does not update packages to pre-release versions for stability reasons. To enable updates to pre-release versions, use
|
@alanhamlett it does not work. Please create a requirements.tx with the following line |
This call to Pip is returning an empty set of candidates for upgrading: pip-update-requirements/pur/utils.py Line 165 in 19d1f64
I've updated pip to the latest version (19.1.dev0) and it's still returning an empty set. The problem could be in how we setup pip-update-requirements/pur/__init__.py Line 332 in 19d1f64
|
seems to be correct. @eLBati Do you get the different result? P.S. odoo12-addon-l10n-it-fatturapa and odoo12-addon-l10n-it-fatturapa-out are two different packages. |
|
@eLBati Thanks, the difference was in Python version, it works with 3.7 but fails with 2.7. Update after some debugging: maybe I am missing something again but |
@alanhamlett I guess the issue can be closed. |
Let's leave this open, since it's not related to that single package and we should support this requirement spec in general. |
I notice that
pur
will not detect updates forblack
(https://github.com/ambv/black).Reproduction of error:
pip install pur
requirements.txt
black==18.6b4
torequirements.txt
pip install -r requirements.txt
black==18.6b4
in output ofpip freeze
pur -f -r requirements.txt
black==18.6b4
in requirements.txtpip install -U black
black==18.9b0
The text was updated successfully, but these errors were encountered: