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 terry.reedy
Recipients JayKrish, Saimadhav.Heblikar, Todd.Rovito, ned.deily, philwebster, python-dev, serhiy.storchaka, terry.reedy, zach.ware
Date 2014-06-09.00:07:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402272479.66.0.864481184109.issue18910@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, early skipping was the reason I put the test where I did. The simple change occurred to me today. I have not decided yet whether to also change the 3.4/5 files to match and how to edit the testing README. For one test, I would not care either way. But I expect there to be more files with the same issue, So I wonder what is the best way to avoid hitting the same booby trap again.
History
Date User Action Args
2014-06-09 00:07:59terry.reedysetrecipients: + terry.reedy, ned.deily, Todd.Rovito, python-dev, zach.ware, serhiy.storchaka, JayKrish, philwebster, Saimadhav.Heblikar
2014-06-09 00:07:59terry.reedysetmessageid: <1402272479.66.0.864481184109.issue18910@psf.upfronthosting.co.za>
2014-06-09 00:07:59terry.reedylinkissue18910 messages
2014-06-09 00:07:59terry.reedycreate