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 r.david.murray
Recipients Claudiu.Popa, koobs, python-dev, r.david.murray, serhiy.storchaka
Date 2013-10-14.15:48:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381765700.45.0.745530186375.issue18919@psf.upfronthosting.co.za>
In-reply-to
Content
In 2.7 unexpected output is a test failure, yes.

In 3.x we removed that check.  But I wonder if that was wise :)  (We did it for technical reasons when adding other features to regrtest).

Yes, using captured_stdout and checking for the expected warnings would be a better test, IMO.
History
Date User Action Args
2013-10-14 15:48:20r.david.murraysetrecipients: + r.david.murray, Claudiu.Popa, python-dev, serhiy.storchaka, koobs
2013-10-14 15:48:20r.david.murraysetmessageid: <1381765700.45.0.745530186375.issue18919@psf.upfronthosting.co.za>
2013-10-14 15:48:20r.david.murraylinkissue18919 messages
2013-10-14 15:48:20r.david.murraycreate