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 chris.jerdonek
Recipients asvetlov, chris.jerdonek, ezio.melotti, gregory.p.smith, serhiy.storchaka, terry.reedy
Date 2012-12-26.09:40:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It's enough not to make the problem worse, which is why I suggested it and what I wanted to avoid.  If you copy-paste the tests you're adding now, it worsens the problem and makes it that much more tedious to fix later on (and to maintain in the meantime).

Why must the code sharing be all or nothing?  Elsewhere we phase in improvements incrementally.  Even with the particular refactoring you're suggesting for the future, I'm not sure we'd want to do it all in one patch.

If you begin the process now and add appropriate comments and TODO's pointing the way, at least the next person will know how to take the next steps.
Date User Action Args
2012-12-26 09:40:47chris.jerdoneksetrecipients: + chris.jerdonek, terry.reedy, gregory.p.smith, ezio.melotti, asvetlov, serhiy.storchaka
2012-12-26 09:40:47chris.jerdoneksetmessageid: <>
2012-12-26 09:40:47chris.jerdoneklinkissue16761 messages
2012-12-26 09:40:47chris.jerdonekcreate