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 eli.bendersky
Recipients eli.bendersky, ezio.melotti, georg.brandl, ncoghlan, python-dev, r.david.murray, vlad
Date 2013-09-13.13:36:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda8ctK91tSX9xDw0HejfWS9v2bp4kLuONMSEVTn6SP4dZA@mail.gmail.com>
In-reply-to <1379078905.95.0.190783422288.issue18945@psf.upfronthosting.co.za>
Content
On Fri, Sep 13, 2013 at 6:28 AM, R. David Murray <report@bugs.python.org>wrote:

>
> R. David Murray added the comment:
>
> We don't generally backport tests unless they are part of a bug fix.  It's
> not a blanket prohibition, but normally the risk of false positives in a
> maintenance release on platforms not covered by our buildbots outweighs the
> benefits of adding the tests.
>

These tests are very related to an actual bug-fix (
http://bugs.python.org/issue18849). Moreover, they cover a previously
uncovered feature which resulted in very intermittent heisen-bugs where
temp file creation was occasionally failing on some platforms. IMHO having
this covered is worth the small maintenance burden of the tests - who
knows, it may uncover real problems. What do you think?
History
Date User Action Args
2013-09-13 13:36:45eli.benderskysetrecipients: + eli.bendersky, georg.brandl, ncoghlan, ezio.melotti, r.david.murray, python-dev, vlad
2013-09-13 13:36:45eli.benderskylinkissue18945 messages
2013-09-13 13:36:45eli.benderskycreate