M
Mike Kent
I'd like to ship only the .pyc files for a module. I was hoping the
standard distutils setup.py could handle this, but so far, I've not
figured out how.
After a bit of work, I discovered that if I create a MANIFEST.in file,
and put 'include mymodule/*.pyc' and 'exclude mymodule/*.py' in it,
then running 'python setup.py sdist' would generate a tar.gz file for
me that contained the setup.py file and all my .pyc files, just like I
wanted. However, when I then extract that tar.gz file, and try to run
'python setup.py install', it complains about the missing .py files,
and creates the 'mymodule' directory in the site-packages directory
but without putting any of the .pyc files in it.
At this point, I'm stumped. I was hoping someone out there had gone
down this same route and could tell what I'm doing wrong. Can
setup.py even handle this?
standard distutils setup.py could handle this, but so far, I've not
figured out how.
After a bit of work, I discovered that if I create a MANIFEST.in file,
and put 'include mymodule/*.pyc' and 'exclude mymodule/*.py' in it,
then running 'python setup.py sdist' would generate a tar.gz file for
me that contained the setup.py file and all my .pyc files, just like I
wanted. However, when I then extract that tar.gz file, and try to run
'python setup.py install', it complains about the missing .py files,
and creates the 'mymodule' directory in the site-packages directory
but without putting any of the .pyc files in it.
At this point, I'm stumped. I was hoping someone out there had gone
down this same route and could tell what I'm doing wrong. Can
setup.py even handle this?