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 gvanrossum
Recipients NeilGirdhar, Rosuav, belopolsky, ethan.furman, gvanrossum, ncoghlan, python-dev, r.david.murray, rhettinger, schlamar, scoder, serhiy.storchaka, vstinner, yselivanov
Date 2015-05-07.20:18:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
I think you could help by (a) reviewing what's there, and (b) helping with
the implementation of __future__.

On Thu, May 7, 2015 at 1:16 PM, Yury Selivanov <>

> Yury Selivanov added the comment:
> > You sure can! Take it, deploy it, run the test suite, and then start
> writing real code that uses it. When you find a problem, that's what needs
> help! :)
> Thank you for this generic answer, Chris.
> The reason I was asking is because issue #24017 depends on this one (also
> release blocker).  And I was genuinely wondering if I can help (somehow)
> advancing your patch to be committed asap.  Anyways, do you have any
> estimate when you finalize it?
> ----------
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2015-05-07 20:18:01gvanrossumsetrecipients: + gvanrossum, rhettinger, ncoghlan, belopolsky, scoder, vstinner, r.david.murray, ethan.furman, python-dev, schlamar, Rosuav, serhiy.storchaka, yselivanov, NeilGirdhar
2015-05-07 20:18:01gvanrossumlinkissue22906 messages
2015-05-07 20:18:01gvanrossumcreate