Message242734
Or, if it's perfect (or good enough :-), just check it in.
On Thu, May 7, 2015 at 1:18 PM, Guido van Rossum <report@bugs.python.org>
wrote:
>
> Guido van Rossum added the comment:
>
> 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 <report@bugs.python.org>
> wrote:
>
> >
> > 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 <report@bugs.python.org>
> > <http://bugs.python.org/issue22906>
> > _______________________________________
> >
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue22906>
> _______________________________________
> |
|
Date |
User |
Action |
Args |
2015-05-07 20:24:38 | gvanrossum | set | recipients:
+ gvanrossum, rhettinger, ncoghlan, belopolsky, scoder, vstinner, r.david.murray, ethan.furman, python-dev, schlamar, Rosuav, serhiy.storchaka, yselivanov, NeilGirdhar |
2015-05-07 20:24:38 | gvanrossum | link | issue22906 messages |
2015-05-07 20:24:38 | gvanrossum | create | |
|