Op 06-01-13 23:03, Jim Fulton schreef:
On Sun, Jan 6, 2013 at 3:51 PM, Reinout van Rees <rein...@vanrees.org> wrote:
On 05-01-13 23:47, Jim Fulton wrote:
1. New buildout option named ``versions-file`` which takes the name of
a file. to contain version information. It is not a configuration
file. It is a file consisting of comments (#...) and version
specifications::
# whatever
foo = 1.3
So... basically pip's requirements.txt?
I'm not familiar with pip's requirements.txt, but I suppose so,
except that over time, this might have versions for things that are
no-longer used, and, as you point out later, it might not be complete.
Pip's requirements.txt (run 'pip freeze') needs version specifications
in the same format as easy_install, so with 'package == 1.0' (double
equals-sign) or 'package >= 2.0', so it is not the same format.
It would probably be saner to generate a pip requirements file from
a buildout-generated script. This wouldn't need a new feature.
A script (or extension, or core buildout) could read the pinned versions
and basically do this:
sed 's/=/==/' versions.cfg > requirements.txt
--
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
