Open termie opened 13 years ago
(by jaypipes) Yet another reason why putting:
dependency==specific-version
in pip-requires is generally not a good thing.
-jay
(by ttx) Our Hudson setup being Ubuntu-based and Ubuntu having pep8 0.5.0 in Maverick and Natty, I suspect the automated tests on trunk are using 0.5.0... hence the pinning for those using pip-requires ?
Any reason why we would want to use pep8 0.6 ?
(by soren) We've used 0.6.1 on the Jenkins box for months and months. Why it's not in Natty is a mystery to me.
2011/2/21 Thierry Carrez thierry@openstack.org:
Our Hudson setup being Ubuntu-based and Ubuntu having pep8 0.5.0 in Maverick and Natty, I suspect the automated tests on trunk are using 0.5.0... hence the pinning for those using pip-requires ?
Any reason why we would want to use pep8 0.6 ?
\ Changed in: nova Status: New => Incomplete
You received this bug notification because you are subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/721867
Title: Use latest pep8 in pip-requires
Soren Hansen | http://linux2go.dk/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/
(by soren) Ah, apparantly 0.6.1 isn't even in Debian yet; Monty just packaged it for us. Maybe he has some insight.
(by ttx) @Monty: any chance you could comment on this ?
We're currently pinning to an old version of pep8. We should probably be using the latest, or at the very least, 0.6.
Imported from Launchpad using lp2gh.