➜

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 larry
Recipients Arfrever, barry, ezio.melotti, larry, michael.foord, pitrou, rbcollins, thomir
Date 2014-02-20.05:49:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392875397.78.0.598466940878.issue20687@psf.upfronthosting.co.za>
In-reply-to
Content 
So here's the thing.  It only works in Python 3.3 because testtools depends on internal implementation details of unittest, specifically a private exception ("unittest.case._UnexpectedSuccess").  The public interface still works fine.  So I don't think this is a regression.  If testtools is willing to release hacks depending on undocumented internal behavior, I don't think it's unreasonable for them to rework their hack to support Python 3.4.

That said, it might be nice to not break testtools if we can avoid it.  Antoine: would it be reasonable to rework the implementation of subTest in a way that permitted us to revert the changes to expectedFailure?
History
Date User Action Args
2014-02-20 05:49:57larrysetrecipients: + larry, barry, pitrou, rbcollins, ezio.melotti, Arfrever, michael.foord, thomir
2014-02-20 05:49:57larrysetmessageid: <1392875397.78.0.598466940878.issue20687@psf.upfronthosting.co.za>
2014-02-20 05:49:57larrylinkissue20687 messages
2014-02-20 05:49:57larrycreate