Similar to pbr, we have a minimum version of setuptools required to
consistently install things in OpenStack. Right now thats 17.1.

However, we don't declare a setup_requires version for it.

I think we should.

setuptools can't self-upgrade, and we don't have declarative deps yet,
so one reaction I expect here is 'how will this help'.

The problem lies in the failure modes. With no dependency declared,
setuptools will try and *silently fail*, or try and fail with this one
weird error - that doesn't say anything about 'setuptools 3.3. cannot
handle PEP 426 version markers'.

If we set a minimum (but not a maximum) setuptools version as a
setup_requires, I think we'll signal our actual dependencies to
redistributors, and folk consuiming python packages, in a much more
direct fashion. They'll still have to recover manually, but thats ok
IMO. As long as we don't set upper bounds, we won't deadlock ourselves
like we did in the past.

-Rob

-- 
Robert Collins <[email protected]>
Distinguished Technologist
HP Converged Cloud

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to