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 jaraco
Recipients ezio.melotti, jaraco, jcea, michael.foord, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, tshepang
Date 2013-11-16.15:44:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A third counterargument is:

3. Newer developers (and even seasoned ones) adding new tests may use existing tests as a model for best practices. If the existing tests model sub-optimal practices, then those practices will be perpetuated both in the codebase and in the minds of contributors.

Given that Serhiy has so diligently prepared and updated the patch, I'm inclined to say the codebase would be better off accepting the patch.

David, can you imagine a process by which a patch like this could be acceptable?
Date User Action Args
2013-11-16 15:44:19jaracosetrecipients: + jaraco, terry.reedy, jcea, pitrou, ezio.melotti, r.david.murray, michael.foord, tshepang, serhiy.storchaka
2013-11-16 15:44:18jaracosetmessageid: <>
2013-11-16 15:44:18jaracolinkissue16510 messages
2013-11-16 15:44:18jaracocreate