This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author abadger1999
Recipients
Date 2006-08-11.15:23:37
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
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.
History
Date User Action Args
2007-08-23 16:12:04adminlinkissue1538778 messages
2007-08-23 16:12:04admincreate