Support 1.x notation in version specifiers
pip team said they won't support setting limit for major version of package being installed in the way below until it is supported by PEP 440. pip install patch==1.x The current way ==1.* conflicts with system shell expansion and the other way is not known / not intuitive. https://github.com/pypa/pip/issues/2737#issuecomment-97621684 -- anatoly t.
Hi!
On Sat, May 02, 2015 at 09:48:42AM +0200, anatoly techtonik
pip team said they won't support setting limit for major version of package being installed in the way below until it is supported by PEP 440.
pip install patch==1.x
This syntax (1.x) is even less intuitive for me.
The current way ==1.* conflicts with system shell expansion
Other comparison operators (< and >) conflict with shell redirection. And nobody cares because one can always quote shell metacharacters. pip install patch==1.\* pip install patch=='1.*' pip install 'patch==1.*' pip install 'patch>=1,<2'
and the other way is not known / not intuitive.
https://github.com/pypa/pip/issues/2737#issuecomment-97621684 -- anatoly t.
Oleg. -- Oleg Broytman http://phdru.name/ phd@phdru.name Programmers don't die, they just GOSUB without RETURN.
On Tue, May 5, 2015 at 6:21 PM, Oleg Broytman
The current way ==1.* conflicts with system shell expansion
Other comparison operators (< and >) conflict with shell redirection. And nobody cares because one can always quote shell metacharacters.
pip install patch==1.\* pip install patch=='1.*' pip install 'patch==1.*' pip install 'patch>=1,<2'
Plus, you can stick anything you like into a requirements.txt and simply 'pip install -r requirements.txt'. That's a safe option - not least since it lets you manage your dependencies in source control. ChrisA
On May 2, 2015, at 00:48, anatoly techtonik
pip team said they won't support setting limit for major version of package being installed in the way below until it is supported by PEP 440.
I think that's misrepresenting them. They explained why it isn't needed, and threw in an "anyway, it's not up to us"; they didn't say "sounds like a good idea, but you have to fix the PEP first". Also, if you can't use pip 6.0 or later to take advantage of the already-working syntax that they recommended you use, how would you be able to use your new syntax even if it did get added?
pip install patch==1.x
The current way ==1.* conflicts with system shell expansion and the other way is not known / not intuitive.
https://github.com/pypa/pip/issues/2737#issuecomment-97621684 -- anatoly t. _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
participants (4)
-
anatoly techtonik
-
Andrew Barnert
-
Chris Angelico
-
Oleg Broytman