On Mon, 2004-04-19 at 16:46, Jeremy Katz wrote:
On Sun, 2004-04-18 at 23:29, seth vidal wrote:
In python packages should the .pyc files be included in the package or not? up2date has them, system-config-users has them, system-config-packages does not, nor does system-config-mouse.
The .pyc files should probably be included as well as the .py files. And it should be done automatically just like the buildroot stripping policies because it's slightly tricky to do "right". Nalin wrote a brp script to do so a while ago, it just hasn't been integrated into the default rpm config (yet)
Any reason to include .py files at all ? Could save some space only shipping the .pyc files..
Nils O. Selåsdal wrote:
Any reason to include .py files at all ? Could save some space only shipping the .pyc files..
Come on, we're talking several kilobytes. :) Debugging .pyc-only files is a pain, and some like to run with optimizations, so making .pyo becomes impossible without .py (afaict).
I don't really think that's much of a burden to have .py files included, considering that most python programs are really light on the size of the source.
Regards,
On Mon, 2004-04-19 at 17:20, Konstantin Ryabitsev wrote:
Nils O. Selåsdal wrote:
Any reason to include .py files at all ? Could save some space only shipping the .pyc files..
Come on, we're talking several kilobytes. :) Debugging .pyc-only files is a pain, and some like to run with optimizations, so making .pyo becomes impossible without .py (afaict).
well if it's for debugging and co... isn't this what the -debuginfo packages can be used for, eg move the .py files there....
-
"Nils O. Selåsdal" -
Arjan van de Ven -
Bill Nottingham -
Konstantin Ryabitsev -
seth vidal