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 Fotis.Koutoulakis
Recipients Fotis.Koutoulakis, docs@python, ezio.melotti, ncoghlan, serhiy.storchaka, seydou
Date 2013-12-09.11:13:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386587593.23.0.413131823195.issue18576@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, here is the second (modified patch) which contains a script so that no modifications are required to existing tests.

I am uploading it as a second patch, so that the first one is left as a reference.

As a sidenote, I fail to see convincing reasons for why we would want the second solution more than the first. The first one looks cleaner to my eyes. The only downside I can see to the original approach is breaking a couple of tests, which is something that can be fixed easily without even making it to the repo (running the tests in 2-3 could help find all possible broken tests beforehand).

Could someone explain to me why the second solution is more desirable?
History
Date User Action Args
2013-12-09 11:13:13Fotis.Koutoulakissetrecipients: + Fotis.Koutoulakis, ncoghlan, ezio.melotti, docs@python, serhiy.storchaka, seydou
2013-12-09 11:13:13Fotis.Koutoulakissetmessageid: <1386587593.23.0.413131823195.issue18576@psf.upfronthosting.co.za>
2013-12-09 11:13:13Fotis.Koutoulakislinkissue18576 messages
2013-12-09 11:13:13Fotis.Koutoulakiscreate