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 r.david.murray
Recipients jamercee, r.david.murray
Date 2014-12-30.15:46:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419954382.75.0.420420461002.issue23129@psf.upfronthosting.co.za>
In-reply-to
Content
(Please trim the original message when replying to a tracker issue.)

When I said, "that probably means it's a doc issue", I meant that, even if it is a bug, for backward compatibility reasons we'd have to just document the behavior.  Fixing the bug would then be a new feature (new keyword to change the behavior or some such).  (ie: the fix to a design bug is a feature :)

Now, if it turns out that the bug lies elsewhere, or that changing the current statement-reset behavior wouldn't actually change the meaning of anyone's program if we changed it, then we could fix it as a bug.  But we'll need to understand the bug in detail before we can make that determination.
History
Date User Action Args
2014-12-30 15:46:22r.david.murraysetrecipients: + r.david.murray, jamercee
2014-12-30 15:46:22r.david.murraysetmessageid: <1419954382.75.0.420420461002.issue23129@psf.upfronthosting.co.za>
2014-12-30 15:46:22r.david.murraylinkissue23129 messages
2014-12-30 15:46:22r.david.murraycreate