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/032270.html below:

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

[Python-Dev] disable writing .py[co] [Python-Dev] disable writing .py[co]Neal Norwitz neal@metaslash.com
Mon, 20 Jan 2003 17:32:04 -0500
In http://python.org/sf/602345 (option for not writing .py[co] files)
Martin suggested that in addition to a flag (-R, as in read-only),
perhaps there should be an env't variable and/or a sys attribute
which controls whether .py[co] files are written or not.

Opinions?  

If you like the idea of an env't variable or sys attribute, do you
have suggestions for names?  PYTHONREADONLY and sys.readonly_import?

Neal




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