* Joey Hess <[email protected]>, 2010-03-31, 16:14:
calling setup.py install with --no-compile hides byte compilation
errors, it would be better to detect these at build time.
Agreed. It should be noted, however, that byte-compiling at build-time is
not as useful for QA purposes as it could be: "setup.py install" exists
with 0 even if there were byte-compilation errors.
please don't call with --no-compile, and remove generated bytecode
files after the setup.py install call.
How can I get a list of all the byte-compiled files it produced?
distutils prints names of byte-compiled files on stdout, like this:
byte-compiling
debian/python-byteplay/usr/lib/python2.7/site-packages/byteplay.py to
byteplay.pyc
You could try parsing this. Chances that the output format will change
in the future are pretty slim, as no major releases of Python 2.X are
planned.
An alternative would be not remove *.py[co] at all and pass this duty to
Python helper (I believe that they already do this) or to the user.
(I see some files ending in .pyc and .pyo in the archive, so deleting
them all seems too strong.)
There shouldn't be any new packages doing that though. Packages for
which lintian emits package-installs-python-bytecode are automatically
rejected by ftp-master.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
