[openstack-dev] [requirements] re-ordered specifiers in requirements.txt
sean at dague.net
Mon Jun 22 10:07:21 UTC 2015
On 06/22/2015 04:33 AM, Robert Collins wrote:
> You may have noticed the every repo has just been spammed with some
> no-op changes where specifiers are re-ordered such as in
> Whats happening is that the requirements code now parses and
> regenerates the specifiers as I mentioned last week. So this is
> normal, but one-time.
So, while I get that it's all equivalent, it's pretty unhuman friendly
to specify this in this order. Can we get >(=)* first, != next, and
<(=)* last so that it reads as a human range?
More information about the OpenStack-dev