# Preparing for new Python parsing

**URL:** <https://discuss.python.org/t/preparing-for-new-python-parsing/1550>\
**Category:** Ideas\
**Created:** [April 25, 2019, 9:28pm UTC](https://discuss.python.org/t/preparing-for-new-python-parsing/1550 "2019-04-25T21:28:54Z")\
**Posts on this page:** 1\
**Showing post:** 100

<div class="post-metadata">

**Author:** ![apalala](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/apalala/32/683_2.png) [@apalala](https://discuss.python.org/u/apalala)\
**Post date:** [July 12, 2019, 3:17pm UTC](https://discuss.python.org/t/preparing-for-new-python-parsing/1550/100 "2019-07-12T15:17:16Z")

</div>

> [@guido](#):
>
> Exciting news: I have been working on generating C code, and a preliminary test shows that it is in the right ballpark. See the [README](https://github.com/gvanrossum/pegen/blob/master/README.md#c-code-generator). The C generator doesn’t yet support the same feature set as the Python generator (missing are left recursion, optional, loops, lookahead, cut), but I’m excited.

Outstanding!

(My apologies for my AWOL of the past few weeks…)

---

_[View the full topic](https://discuss.python.org/t/preparing-for-new-python-parsing/1550)._