On Thu, Jan 3, 2013 at 1:27 PM, Reinout van Rees <rein...@vanrees.org> wrote: > On 03-01-13 14:03, Marius Gedminas wrote: > >> I consider buildout-versions to be essential for my use of buildout. > > > Agreed. I'm using 2.0a for a personal project now, but I cannot > realistically use it for projects I work on with others without something > like buildout-versions. > > Personally, a "warn-about-picked-versions = true" setting name sounds too > harsh. For me, "print-unpicked-versions" would be a better indication of > what I want. Just a list of pins that's printed after buildout is finished > that I can copy/paste into my buildout config if I want to pin them.
I don't know about 2.0, but in the 1.x line of buildout some number of -v options will give you a list of picked versions that is easy to transmute into a versions.cfg. Here is the config I use in Vim to add a :MungeVersions command that takes the -vvvv output in the current buffer and makes it into "PACKAGE = VERSION" lines: com! -bar MungeVersionsGrep %!grep "Picked:" com! MungeVersions silent MungeVersionsGrep | silent %s/Picked: // | %sort | silent %!uniq It is just a tiny shell script wrapped in a candy coating. -- Benji York _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
