[openstack-dev] [requirements][packaging] Normalizing requirements file

Tony Breeds tony at bakeyournoodle.com
Fri Jun 24 02:02:38 UTC 2016

On Wed, Jun 22, 2016 at 03:23:43PM +1000, Tony Breeds wrote:
> On Wed, Jun 22, 2016 at 06:45:31AM +0200, Haïkel wrote:
> > Hi,
> > 
> > as a packager, I spend a lot of time to scrutinize the requirements
> > repo, and I find it easier to read if specifiers are ordered.
> > So in a quick glance, you can check which is the min version required
> > and max one without trying to search them among other specifiers.
> > I scripted a basic linter to do that (which also normalize comments to
> > PEP8 standards)
> > 
> > Initial review is here:
> > https://review.openstack.org/#/c/332623/
> > 
> > script is available here;
> > https://gist.github.com/hguemar/7a17bf93f6c8bd8ae5ec34bf9ab311a1
> > 
> > Your thoughts?
> I'm fine with doign something like this.  I wrote [1] some time ago but didn't
> push on it as I needed to verify that this wouldn't create a "storm" of
> pointless updates that just reorder things in every projects *requirements.txt.

I think we need to pause on these 'normalizing' changes in g-r.  They're
genertaing whitspace only reviews in many, (possibly all) projects that have
managed requirements.

We need to do more testing and possibly make the bot smarter befoer we look at
this again.

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160624/b6a9a86c/attachment.pgp>

More information about the OpenStack-dev mailing list