On Fri, Jan 25, 2013 at 3:53 PM, Reinout van Rees rein...@vanrees.org wrote:
On 16-01-13 13:52, Jim Fulton wrote:
On Sat, Jan 12, 2013 at 11:18 AM, Jim Fulton j...@zope.com wrote:
On Sat, Jan 5, 2013 at 5:47 PM, Jim Fulton j...@zope.com wrote:
...
I propose that buildout-versions get
On Mon, Jan 28, 2013 at 6:38 AM, Jim Fulton j...@zope.com wrote:
On Fri, Jan 25, 2013 at 3:53 PM, Reinout van Rees rein...@vanrees.org wrote:
...
3. New buildout option: ``python-version`` that restricts the Python
version, with the same semantics as buildout-version provides now.
Hm.
On 28-01-13 12:50, Jim Fulton wrote:
On Mon, Jan 28, 2013 at 6:38 AM, Jim Fulton j...@zope.com wrote:
On Fri, Jan 25, 2013 at 3:53 PM, Reinout van Rees rein...@vanrees.org wrote:
...
3. New buildout option: ``python-version`` that restricts the Python
version, with the same semantics
On 28-01-13 13:17, Reinout van Rees wrote:
I should have mentioned that an option is to defer the python-version
feature for later.
I'll take the python version out of my pull request for now and create a
separate issue that points at the removed code.
I've updated the pull request.
Travis
On Mon, Jan 28, 2013 at 2:56 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Mon, Jan 28, 2013 at 5:17 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Mon, Jan 28, 2013 at 4:58 PM, Tarek Ziadé ta...@ziade.org wrote:
On 1/28/13 7:17 AM, Nick Coghlan wrote:
...
3. There needs to be a
buenas:
me pierdo como, donde se instala scapy para que funcione bajo el programa
python version 3.3.0
gracias y saludos:
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
On 10-01-13 19:08, MIGUEL ANGEL FERNANDEZ ANDRES wrote:
me pierdo como, donde se instala scapy para que funcione bajo el
programa python version 3.3.0
Ik versta hier geen klap van. (That was Dutch)
= This list is in English, so could you translate your question?
Reinout
--
Reinout van Rees
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Recently I have started a new project that needs some runtime configuration.
All the open sources projects I have reviewed, do the configuration step
by usually deriving from the build_ext command class, and then execute
some configuration code
On 28 January 2013 13:26, Daniel Holth dho...@gmail.com wrote:
We had a discussion about version schemes a while back along with Vinay. It
seems to me that the Major.Minor.Micro sorting is pretty much universal, but
when you want to compare alphanumeric patch / rc versions within the same
On Mon, Jan 28, 2013 at 10:01 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 28 January 2013 13:26, Daniel Holth dho...@gmail.com wrote:
We had a discussion about version schemes a while back along with Vinay.
It
seems to me that the Major.Minor.Micro sorting is pretty much universal,
but
Sounds nice,
Looks like it could make building distributions based on c-libraries
more predictable (think lxml or pymsql), specially when you explicitly
want to avoid libraries provided by the system.
Of course, it would only be helpful for me if buildout grew support
for tweaking it somehow.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/01/2013 19:05, Leonardo Rochael Almeida ha scritto:
Sounds nice,
Looks like it could make building distributions based on c-libraries
more predictable (think lxml or pymsql), specially when you explicitly
want to avoid libraries provided
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In a project I'm working on, I use git, and I'm trying to follow the
versioning scheme used by the git project (since it is very pratical).
To summarize, git version is generated from the output of
git describe command, replacing the '-'
On 01/28/2013 07:12 PM, Manlio Perillo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/01/2013 19:05, Leonardo Rochael Almeida ha scritto:
Sounds nice,
Looks like it could make building distributions based on c-libraries
more predictable (think lxml or pymsql), specially when you
Nick Coghlan ncoghlan at gmail.com writes:
As a simple proposal: a new Version-Scheme field, with currently
supported values setuptools and pep386, and a clause allowing
future pepXYZ versioning schemes. The version scheme field then
effectively defines how versions are sorted for ordered
On Monday, January 28, 2013 at 6:44 PM, Vinay Sajip wrote:
I would add to the currently supported values semantic (http://semver.org/)
as this scheme is widely used and is easy to support.
Currently, distlib supports a number of version schemes:
legacy - setuptools ordering - most liberal
On Monday, January 28, 2013 at 10:58 PM, Daniel Holth wrote:
I would very much like to move everyone to semver (in practice a subset that
is compatible with the file naming conventions, you probably won't get far if
your version contains a dash -). The setuptools behaviour is the most
I would very much like to move everyone to semver (in practice a subset
that is compatible with the file naming conventions, you probably won't get
far if your version contains a dash -). The setuptools behaviour is the
most practical scheme in use in the Python community. I've made most of the
18 matches
Mail list logo
