# 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:** 42

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [May 24, 2019, 6:43am UTC](https://discuss.python.org/t/preparing-for-new-python-parsing/1550/42 "2019-05-24T06:43:57Z")

</div>

> [@apalala](#):
>
> A `cut` parses nothing, but the parser commits to the current choice after it sees it.

Question about this (it’s keeping me up :-). Does failure to match what follows `~` cause the _entire parse_ to fail (a `panic` if you will), or does it just skip further alternatives of the current rule, while still allowing further alternatives of “callers” to be probed?

---

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