[Distutils] RFC PEP 386 : Version comparisons

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tarek Ziadé wrote:

> back to that discussion, after re-reading all the threads I have a proposal :
> 
> 1- let's add as we said "install_requires" in PEP 345 and describe in
> it that people can define requirements,
>   but without giving them rules for the version schemes.
> 
>   We will just write in that PEP that it's up to the *dependency
> manager* (pip, setuptools, zc.buildout, etc)
>   to provide a cmp() for the version.
> 
>   The only rule will be that each dependency is described like this :
> 
>      dist_name [<|>|==|!=|>=|<=] version
> 
>   where version is free and dist_name in [a-zA-Z0-9]
> 
> 2- let's drop PEP 386 completely

- -1.  I would rather exclude some use cases (post releases), than drop
standardization altogether.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKT5um+gerLs4ltQ4RAgCsAJ9D0yLYkd4vkkVhZ81CMclJWO1T4ACgiVjd
bDq3s9KO/oV0LDtmYDeXHe0=
=gUpQ
-----END PGP SIGNATURE-----