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 jvs
Recipients barry, jvs, rhettinger
Date 2015-01-12.15:17:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421075866.75.0.0324327151196.issue23189@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that -OO does what (people have agreed) it's supposed to do.

Many packages manipulates the docstring without checking for 'None' (see list below). For many package developers, it seems hard to remember that the docstrings may disappear after optimization. This behavior is not intuitive. At least in cases where the docstring is set to a string value, the expected behavior in my opinion would be to set its value to an empty string during optimization with -OO.

Here are some of the packages that run into trouble when the docstrings are set to 'None' by the -OO optimization:
algopy
astropy
lmfit
pyamg
pyvisa
mpl_toolkits
sympy
statsmodels
patsy
sklearn
History
Date User Action Args
2015-01-12 15:17:46jvssetrecipients: + jvs, barry, rhettinger
2015-01-12 15:17:46jvssetmessageid: <1421075866.75.0.0324327151196.issue23189@psf.upfronthosting.co.za>
2015-01-12 15:17:46jvslinkissue23189 messages
2015-01-12 15:17:46jvscreate