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 collinwinter
Recipients benjamin.peterson, collinwinter, georg.brandl, rbp, rhettinger
Date 2008-07-22.04:04:36
SpamBayes Score 0.20796692
Marked as misclassified No
Message-id <1216699479.86.0.830949462679.issue3417@psf.upfronthosting.co.za>
In-reply-to
Content
I think the proper way to address this is via the confidence levels that
Rodrigo Bernardo Pimentel is adding for his Summer of Code project. The
idea is that you'll be able to say "let me inspect any changes where the
fixer is less than X% confident". fix_dict and for loops would be one
such place.

Until that mechanism is in place, I agree with Raymond that we should
err on the side of correctness.
History
Date User Action Args
2008-07-22 04:04:40collinwintersetspambayes_score: 0.207967 -> 0.20796692
recipients: + collinwinter, georg.brandl, rhettinger, benjamin.peterson, rbp
2008-07-22 04:04:39collinwintersetspambayes_score: 0.207967 -> 0.207967
messageid: <1216699479.86.0.830949462679.issue3417@psf.upfronthosting.co.za>
2008-07-22 04:04:38collinwinterlinkissue3417 messages
2008-07-22 04:04:37collinwintercreate