A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] disable writing .py[co] [Python-Dev] disable writing .py[co]Barry A. Warsaw barry@python.org
Wed, 22 Jan 2003 07:49:04 -0500
>>>>> "MvL" =3D=3D Martin v L=F6wis <martin@v.loewis.de> writes:

    MvL> The real problem here is that some people don't want Python
    MvL> to write any .pyc files, period. So even if mailman
    MvL> byte-compiles all its source code, it can't stop Python from
    MvL> writing .pyc files that belong to mailman. That, in turn, can
    MvL> cause the problems discussed in this thread: there might be
    MvL> races in doing so, it might trigger security alarms, and it
    MvL> might write byte code files in configuration areas of the
    MvL> system where only text files are allowed, per policy.

I'm not against suppressing or redirecting pyc output.  I kind of like
Skip's approach.

-Barry



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