# PEP 827: Type Manipulation

**URL:** <https://discuss.python.org/t/pep-827-type-manipulation/106353>\
**Category:** PEPs\
**Created:** [March 2, 2026, 6:05pm UTC](https://discuss.python.org/t/pep-827-type-manipulation/106353 "2026-03-02T18:05:15Z")\
**Posts on this page:** 1\
**Showing post:** 62

<div class="post-metadata">

**Author:** ![dr\_carlos](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/dr_carlos/32/30461_2.png) [@dr\_carlos](https://discuss.python.org/u/dr_carlos)\
**Post date:** [March 5, 2026, 10:08pm UTC](https://discuss.python.org/t/pep-827-type-manipulation/106353/62 "2026-03-05T22:08:13Z")

</div>

> [@msullivan](#):
>
> Right, but if we added the strings to ` __annotate__ ` and switch `Format.STRING` to calling ` __annotate__ ` with `Format.STRING` , I think we would be in OK shape because it would be possible to extract the appropriate context from the closure of ` __annotate__ `? (Though maybe `annotationlib` would want to expose a function to help facilitate this.)

@DavidCEllis has a proposal to add a new helper which is like ‘just store the strings’ but stores that relevant context and supports evaluation, etc.

See [the discussion here](https://discuss.python.org/t/add-a-format-deferred-option-for-pep-649-749-annotations/104001)

Edit: fixed broken link

---

_[View the full topic](https://discuss.python.org/t/pep-827-type-manipulation/106353)._