# PEP 709: Inlined comprehensions

**URL:** <https://discuss.python.org/t/pep-709-inlined-comprehensions/24240>\
**Category:** PEPs\
**Created:** [February 25, 2023, 5:39pm UTC](https://discuss.python.org/t/pep-709-inlined-comprehensions/24240 "2023-02-25T17:39:02Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![timfelgentreff](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/timfelgentreff/32/4147_2.png) [@timfelgentreff](https://discuss.python.org/u/timfelgentreff)\
**Post date:** [February 28, 2023, 9:35am UTC](https://discuss.python.org/t/pep-709-inlined-comprehensions/24240/20 "2023-02-28T09:35:07Z")

</div>

Since GraalPy tries to not lag behind CPython more than a year or so, we would be affected by this. Even if it might be considered a minor visible effect and/or an implementation detail, it is always surprising (to me) how much of those details end up being relied upon 🙂

Because of details such as this we have recently switched to re-using the PEG parser and following the CPython bytecode compiler as closely as we possibly can, so I think that we would just pick up those same changes in observable behaviour without much headache.

---

_[View the full topic](https://discuss.python.org/t/pep-709-inlined-comprehensions/24240)._