[Python-bugs-list] [ python-Bugs-602345 ] option for not writing .py[co] files

[noreply@sourceforge.net]

Bugs item #602345, was opened at 2002-08-30 07:13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=602345&group_id=5470

Category: Python Interpreter Core
Group: Feature Request
Status: Open
Resolution: None
Priority: 3
Submitted By: Matthias Klose (doko)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: option for not writing .py[co] files

Initial Comment:
[destilled from http://bugs.debian.org/96111]

Currently python tries to write the .py[co] files even
in situations, where it will fail, like on read-only
mounted file systems.

In other situations I don't want python trying to write
the compiled files, i.e. having installed the modules
as root as part of a distribution, compiled them
correctly, there is no need to write them. Or compiling
.py files which are configuration files.

Is it reasonable to add an option to python
(--dont-write-compiled-files) to the interpreter, which
doesn't write them? This would not affect existing code
at all.


----------------------------------------------------------------------

>Comment By: Guido van Rossum (gvanrossum)
Date: 2002-09-03 11:39

Message:
Logged In: YES 
user_id=6380

I think it's a good idea, but please use a single upper case
letter for the option. Python doesn't support long options
and I'm not about to start doing so.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2002-09-01 19:30

Message:
Logged In: YES 
user_id=33168

Guido, do you think this is a good idea?  If so, assign back
to me and I'll work up a patch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=602345&group_id=5470