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 Rosuav
Recipients NeilGirdhar, Rosuav, belopolsky, ethan.furman, gvanrossum, ncoghlan, python-dev, r.david.murray, rhettinger, schlamar, scoder, serhiy.storchaka, vstinner
Date 2015-04-27.13:24:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Had a peek at the 2.7 branch in the web ( and all the tests appear to be testing the behaviour *with* the future directive, not bothering to test the old behaviour. It makes sense - that way, when the future directive becomes permanent, there's no suddenly-failing test - can someone confirm that that's the intention?

The current test simply triggers a StopIteration and verifies that RuntimeError comes up off it, without testing the current behaviour, nor testing any of the aspects that haven't changed. I'm basically assuming that generators themselves are adequately tested elsewhere, such that a bug in the PEP 479 code that breaks generators in any other way should be caught by a test failure someplace else. Can anyone think of other aspects of PEP 479 that need to be tested?
Date User Action Args
2015-04-27 13:24:43Rosuavsetrecipients: + Rosuav, gvanrossum, rhettinger, ncoghlan, belopolsky, scoder, vstinner, r.david.murray, ethan.furman, python-dev, schlamar, serhiy.storchaka, NeilGirdhar
2015-04-27 13:24:43Rosuavsetmessageid: <>
2015-04-27 13:24:42Rosuavlinkissue22906 messages
2015-04-27 13:24:42Rosuavcreate