➜

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 ncoghlan
Recipients mitchchapman, mnot, ncoghlan, nnorwitz, twouters, zseil
Date 2007-12-03.13:03:08
SpamBayes Score 0.24290143
Marked as misclassified No
Message-id <1196686988.78.0.373611096291.issue1510172@psf.upfronthosting.co.za>
In-reply-to
Content 
PEP 366 has been implemented for 2.6, which fixes this bug. The fix
turned out to be quite invasive (hence the PEP), so it won't be
backported to 2.5.
History
Date User Action Args
2007-12-03 13:03:09ncoghlansetspambayes_score: 0.242901 -> 0.24290143
recipients: + ncoghlan, twouters, nnorwitz, mitchchapman, zseil, mnot
2007-12-03 13:03:08ncoghlansetspambayes_score: 0.242901 -> 0.242901
messageid: <1196686988.78.0.373611096291.issue1510172@psf.upfronthosting.co.za>
2007-12-03 13:03:08ncoghlanlinkissue1510172 messages
2007-12-03 13:03:08ncoghlancreate