[Python-ideas] bdist naming scheme (compatibility tags) PEP
mal at egenix.com
Wed Aug 8 13:56:17 CEST 2012
Daniel Holth wrote:
> Today pypy and CPython's "setup.py bdist" generate the same filename
> but incompatible bdists.
The distutils "bdist" command is just a generic command which then
runs one of the more specific bdist_* commands (via the --formats
option; defaulting to bdist_dumb).
Since each of these produces different output files (installers,
packages, eggs, etc), you should be more specific about which
command you are referring to.
Reading the PEP, I assume you'd like to change the bdist_dumb output
file name only.
> This makes it difficult to share both bdists
> in the same folder or index. Instead, they should generate different
> bdist filenames because one won't work with the other implementation.
> This PEP specifies a tagging system that includes enough information
> to decide whether a particular bdist is expected to work on a
> particular Python.
> Also at https://bitbucket.org/dholth/python-peps/raw/98cd36228c2e/pep-CTAG.txt
> Thanks for your feedback,
> Daniel Holth
> Python-ideas mailing list
> Python-ideas at python.org
Professional Python Services directly from the Source (#1, Aug 08 2012)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2012-08-25: FrOSCon, St. Augustin, Germany ... 17 days to go
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the Python-ideas