[Python-Dev] Killing off bdist_dumb (original) (raw)
M.-A. Lemburg mal@lemburg.com
Fri, 15 Nov 2002 18:11:50 +0100
- Previous message: [Python-Dev] Killing off bdist_dumb
- Next message: [Python-Dev] Killing off bdist_dumb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Heller wrote:
I have more the impression, that people release .tar.gz files containing a distutils setup.py script, but no PKG-INFO, so the tarball isn't created by distutils sdist command. PyChecker is such an example, IIRC.
This is correct. I do release PyChecker as a .tar.gz which contains a setup.py, but no PKG-INFO. Should there be one? I don't use setup.py to create the .tar.gz. I only noticed this (and your package is not the only one) when I worked on a PEP 243 (?, package upload mechinism) implementation where uploaded files would be scanned for the PKG-INFO metadata. I've never found the proper way to make releases when I looked. But that was a long time ago.
I normally don't use Linux, but does 'python setup.py sdist' not work there?
It works just fine. All you have to watch out for is to provide a proper MANIFEST.in or MANIFEST file which tells distutils which files to include in the source distribution (command sdist).
-- Marc-Andre Lemburg CEO eGenix.com Software GmbH
eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
- Previous message: [Python-Dev] Killing off bdist_dumb
- Next message: [Python-Dev] Killing off bdist_dumb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]