[ python-Feature Requests-1538778 ] pyo's are not overwritten by different optimization levels

[SourceForge.net]

Feature Requests item #1538778, was opened at 2006-08-11 17:23
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1538778&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Python Interpreter Core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Toshio Kuratomi (abadger1999)
Assigned to: Nobody/Anonymous (nobody)
Summary: pyo's are not overwritten by different optimization levels

Initial Comment:
If I invoke "python -OO" on a set of files, python
creates a set of .pyo files.  If I then realize this is
an incredibly stupid thing to do because it removes the
docstrings from the output and this program requires
those docstrings python does not give me a method of
overwriting the generated .pyos.

I anticipated that running "python -O" would detect
that the already generated .pyos were created in a
different optimixation level and overwrite them with
new .pyos.  Barring that, I expected there to be a
command line switch to tell python to overwrite the
previously generated .pyo cache files.  Finding
neither, I realized that the only way to recover
docstrings for people using python -O was to rm all the
generated .pyo files.  This seems like a bug or a
missing feature.

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

>Comment By: Martin v. Löwis (loewis)
Date: 2006-08-16 15:18

Message:
Logged In: YES 
user_id=21627

This is a feature request; classifying it as such. See also
PEP 304 (notice it has been withdrawn).

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

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