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 ncoghlan
Recipients NeilGirdhar, Rosuav, belopolsky, ethan.furman, gvanrossum, ncoghlan, python-dev, r.david.murray, rhettinger, schlamar, scoder, serhiy.storchaka, vstinner
Date 2015-03-18.14:49:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Bumped to release blocker so we make sure to look at this at the PyCon sprints, if not before. (I'm assuming Larry's not taking release blocker literally for the 3.5 alphas)

As Neil notes, this patch needs some explicit tests for the new behaviour when the future flag is set.

From a docs point of view, the changes to the language reference itself currently seem surprisingly small, but I haven't looked through in detail to see where other updates might be needed, or how the already modified section could be better updated to account for the impact of the __future__ directive (the current update there doesn't mention that the behaviour is in the process of changing)
Date User Action Args
2015-03-18 14:49:42ncoghlansetrecipients: + ncoghlan, gvanrossum, rhettinger, belopolsky, scoder, vstinner, r.david.murray, ethan.furman, python-dev, schlamar, Rosuav, serhiy.storchaka, NeilGirdhar
2015-03-18 14:49:42ncoghlansetmessageid: <>
2015-03-18 14:49:42ncoghlanlinkissue22906 messages
2015-03-18 14:49:42ncoghlancreate