On Thu, Nov 5, 2009 at 9:31 PM, Sridhar Ratnakumar
<sridh...@activestate.com> wrote:
> Hi,
>
> While reading the PEP I noticed that there seems to be no straightforward to
> specify the package release versions.
>
> >>> egginfo_dirname('python-ldap', '2.3.10')
> 'python_ldap-2.3.10.egg-info'
>
> Consider the following PyPM package file name:
>
> python-ldap-2.3.10_linux-x86_2.6_2.pypm
>
> Here 2.3.10 is python-ldap's version, 2.6 is the Python version .. and 2
> (the last component) is the binary release number (for ActiveState
> repository). This is to upgrade previous releases of the same python-ldap
> (say, python-ldap-2.3.10_linux-x86_2.6_1.pypm).
If I understand correctly, ActiveState has its own releases of
python-ldap repackaged in pypm files,
and has several releases per python-ldap versions.
So, why it doesn't have its own versions ? like: 2.3.10.2 in that
case. (following a PEP 386-compatible scheme)
So this would be:
>>> egginfo_dirname('python-ldap', '2.3.10.2')
'python_ldap-2.3.10.2.egg-info'
Tarek
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
