[Python-Dev] disable writing .py[co] (original) (raw)
Martin v. L�wis martin@v.loewis.de
22 Jan 2003 15:27:04 +0100
- Previous message: [Python-Dev] disable writing .py[co]
- Next message: [Python-Dev] Re: disable writing .py[co]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum <guido@python.org> writes:
Sorry, I still don't understand why shipping an mmcfg.pyc (that's ignored because mmcfg.py is newer) is a problem. Or is Debian shipping only .pyc files?
If you ship it, and the user modifies it, the .pyc file will be outdated, and regenerated the next time mailman is run. Right? This is a problem in itself - python will try to write a .pyc file, even if one was originally distributed.
Furthermore, mm_cfg is located in /etc/mailman/mm_cfg.py. I believe, as a policy, you should not have binary files in /etc.
Regards, Martin
- Previous message: [Python-Dev] disable writing .py[co]
- Next message: [Python-Dev] Re: disable writing .py[co]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]