Guido van Rossum added the comment: Well that would break a lot of code... On May 5, 2015 5:18 PM, "STINNER Victor" <rep...@bugs.python.org> wrote:
> > STINNER Victor added the comment: > > Would it be possible to push the first part of the implementation (without > __future__) just to unblock the implementation of the PEP 492 (issue > #24017: async/await)? > > Later push the second part for __future__. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue22906> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22906> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
