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
> https://review.openstack.org/#/c/193973/1/test-requirements.txt
>
> where
> sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
> ->
> sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
>
> 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?
-Sean
--
Sean Dague
http://dague.net
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
