#36978: Should django evaluate typing annotations at all?
-------------------------------------+-------------------------------------
Reporter: 93578237 | Owner: (none)
Type: Uncategorized | Status: closed
Component: Core (Other) | Version: 5.2
Severity: Normal | Resolution: invalid
Keywords: typing, inspect, | Triage Stage:
deferred annotations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* component: Uncategorized => Core (Other)
* resolution: => invalid
* status: new => closed
Comment:
Thanks, but I don't quite follow, doesn't `FORWARDREF` leave the
annotations unevaluated? I think I benched this at the time and found it
was faster than `STRING. It's also more friendly for any package extending
Django's behavior, since it makes fewer assumptions.
--
Ticket URL: <https://code.djangoproject.com/ticket/36978#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cce1892ba-5efaa47e-ac61-4390-8a2a-245a14bb0a40-000000%40eu-central-1.amazonses.com.
