➜

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 complex
Recipients complex
Date 2007-09-09.00:50:00
SpamBayes Score 0.008783748
Marked as misclassified No
Message-id <1189299001.42.0.803496677722.issue1134@psf.upfronthosting.co.za>
In-reply-to
Content 
Works fine (does nothing) with Python 2.4.4 and Python 2.5.1 under Windows, so this bug must be caused by some new code in Python3.0a1. The bug depends on the contents of the doc string. There's another strange behavior if you write the word "this" in the docstring somewhere. The docstring could be parsed as source code somehow and causes strange things to the new parser.
History
Date User Action Args
2007-09-09 00:50:01complexsetspambayes_score: 0.00878375 -> 0.008783748
recipients: + complex
2007-09-09 00:50:01complexsetspambayes_score: 0.00878375 -> 0.00878375
messageid: <1189299001.42.0.803496677722.issue1134@psf.upfronthosting.co.za>
2007-09-09 00:50:01complexlinkissue1134 messages
2007-09-09 00:50:01complexcreate