Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2003-January/032330.html below:

[Python-Dev] disable writing .py[co]

• 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 mm_cfg.pyc (that's
> ignored because mm_cfg.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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4