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 ned.deily, r.david.murray, ronaldoussoren, willingc
Date 2016-06-24.13:59:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466776794.89.0.625316933235.issue5225@psf.upfronthosting.co.za>
In-reply-to
Content
Why is it out of date?  Did Ned solve this another way at some point?

What I'm getting at is just closing an issue as "out of date" is not enough, really, it is best to record *why* the issue is out of date.
History
Date User Action Args
2016-06-24 13:59:54r.david.murraysetrecipients: + r.david.murray, ronaldoussoren, ned.deily, willingc
2016-06-24 13:59:54r.david.murraysetmessageid: <1466776794.89.0.625316933235.issue5225@psf.upfronthosting.co.za>
2016-06-24 13:59:54r.david.murraylinkissue5225 messages
2016-06-24 13:59:54r.david.murraycreate