Building a platform-independent dist?
It's been several months since I created a distribution using the bdist command. Now I can't seem to build a simple gztar distribution. My MANIFEST.in looks like this: include README RELEASE-NOTES LICENSE MANIFEST include lockfile.py setup.py ACKS recursive-include doc *.rst conf.py Makefile MANIFEST is: ACKS LICENSE MANIFEST README RELEASE-NOTES lockfile.py setup.py doc/glossary.rst doc/index.rst doc/lockfile.rst and I'm executing python setup.py bdist --formats=gztar (where python is 2.7a2+). The output is a .tar.gz file but it includes ".macosx-10.4-i386" in the filename and the tar file itself has more structure and fewer files than I think it should have: % tar tfz dist/lockfile-0.8.macosx-10.4-i386.tar.gz ./ ./Users/ ./Users/skip/ ./Users/skip/local/ ./Users/skip/local/lib/ ./Users/skip/local/lib/python2.7/ ./Users/skip/local/lib/python2.7/site-packages/ ./Users/skip/local/lib/python2.7/site-packages/lockfile-0.8-py2.7.egg-info ./Users/skip/local/lib/python2.7/site-packages/lockfile.py ./Users/skip/local/lib/python2.7/site-packages/lockfile.pyc setup.py is simple: from distutils.core import setup setup(name='lockfile', ... bunch of kwd args elided ... ) Where are the missing files? How do I create a platform-independent distribution? -- Skip Montanaro - skip@pobox.com - http://www.smontanaro.net/
On Tue, Feb 9, 2010 at 2:45 AM,
(where python is 2.7a2+). The output is a .tar.gz file but it includes ".macosx-10.4-i386" in the filename and the tar file itself has more structure and fewer files than I think it should have:
The macosx-10.4-i386 bit is normal since you are building a binary distribution.
% tar tfz dist/lockfile-0.8.macosx-10.4-i386.tar.gz ./ ./Users/ ./Users/skip/ ./Users/skip/local/ ./Users/skip/local/lib/ ./Users/skip/local/lib/python2.7/ ./Users/skip/local/lib/python2.7/site-packages/ ./Users/skip/local/lib/python2.7/site-packages/lockfile-0.8-py2.7.egg-info ./Users/skip/local/lib/python2.7/site-packages/lockfile.py ./Users/skip/local/lib/python2.7/site-packages/lockfile.pyc
That's a strange output, it should build a tree corresponding to the mac platform installation scheme, but here it seems to use a user tree. so is should be: ./Library/Frameworks/Python.framework/.... or ./usr/local/lib/python2.7/... depending on how you have installed Python; instead of ./Users/skip/...
setup.py is simple:
from distutils.core import setup setup(name='lockfile', ... bunch of kwd args elided ... )
Where are the missing files?
I'd need to see the full setup.py options.
How do I create a platform-independent distribution?
By using the "sdist" command. bdist will compile and generate platform-specific distributions. Tarek -- Tarek Ziadé | http://ziade.org
>> How do I create a platform-independent distribution? Tarek> By using the "sdist" command. bdist will compile and generate Tarek> platform-specific distributions. *dope slap* Thanks, Skip
On Tue, Feb 9, 2010 at 11:11 PM,
>> How do I create a platform-independent distribution?
Tarek> By using the "sdist" command. bdist will compile and generate Tarek> platform-specific distributions.
*dope slap*
Thanks,
Notice that I'm interested in understanding how you got that "local" in your bdist... Is your python installed in "./Users/skip/local" ? Tarek -- Tarek Ziadé | http://ziade.org
Tarek> Notice that I'm interested in understanding how you got that Tarek> "local" in your bdist... Tarek> Is your python installed in "./Users/skip/local" ? Well, /Users/skip/local. I never install Python of any variety from source anywhere close to the system locations (not even /usr/local).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 skip@pobox.com wrote:
It's been several months since I created a distribution using the bdist command. Now I can't seem to build a simple gztar distribution. My MANIFEST.in looks like this:
include README RELEASE-NOTES LICENSE MANIFEST include lockfile.py setup.py ACKS recursive-include doc *.rst conf.py Makefile
MANIFEST is:
ACKS LICENSE MANIFEST README RELEASE-NOTES lockfile.py setup.py doc/glossary.rst doc/index.rst doc/lockfile.rst
and I'm executing
python setup.py bdist --formats=gztar
(where python is 2.7a2+). The output is a .tar.gz file but it includes ".macosx-10.4-i386" in the filename and the tar file itself has more structure and fewer files than I think it should have:
Why do you want to make a "dumb" bdist rather than an sdist? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktxxuIACgkQ+gerLs4ltQ64FACfYiXLsAs/i6DnrRyhLbn14VQy qzYAn1eQWzD+Z/y0LjQrMqSc/vk6wnXF =tQjw -----END PGP SIGNATURE-----
participants (3)
-
skip＠pobox.com -
Tarek Ziadé -
Tres Seaver