A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Proto-PEP regarding writing bytecode files

[Python-Dev] Proto-PEP regarding writing bytecode files [Python-Dev] Proto-PEP regarding writing bytecode filesBarry A. Warsaw barry@python.org
Thu, 23 Jan 2003 11:16:32 -0500
>>>>> "TD" == Timothy Delaney <tdelaney@avaya.com> writes:

    TD> I think this is wrong behaviour. IMO it should be as follows:

    TD> - If not present Python bytecode is generated in exactly the
    TD>   same way as is currently done.

    TD> - If present and it refers to an existing directory, bytecode
    TD>   files are written into a directory structure rooted at that
    TD>   location.

    TD> - If present but empty, generation of bytecode files is
    TD>   suppressed altogether.

    TD> - If present and it does not refer to an existing directory,
    TD>   a warning is displayed and generation of bytecode files is
    TD>   suppressed altogether.

+1 for exactly the reasons you state.

-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