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 yselivanov
Recipients gvanrossum, martin.panter, ncoghlan, python-dev, skrah, vstinner, yselivanov
Date 2015-07-22.22:02:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437602529.25.0.189638732694.issue24619@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm just curious if the 'ctx' is still needed:  It looks like
> the outermost "async def" dominates all further nested scopes
> w.r.t the tokenizer mode, no matter whether they're "def" or
> "async def" scopes.

This is a wonderful idea, that's the way it should be done in
both tokenizer.c and tokenize.py.

Please see the new patch.  I love the simplicity of it, no 
more stacks or hard to follow code.
History
Date User Action Args
2015-07-22 22:02:09yselivanovsetrecipients: + yselivanov, gvanrossum, ncoghlan, vstinner, skrah, python-dev, martin.panter
2015-07-22 22:02:09yselivanovsetmessageid: <1437602529.25.0.189638732694.issue24619@psf.upfronthosting.co.za>
2015-07-22 22:02:09yselivanovlinkissue24619 messages
2015-07-22 22:02:09yselivanovcreate