#36696: Using deferred annotations on signals, tasks, etc. in Python 3.14 raises
NameError
-------------------------------------+-------------------------------------
Reporter: Patrick Rauscher | Owner: Patrick
| Rauscher
Type: Bug | Status: closed
Component: Utilities | Version: 5.2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
typing,inspect,deferred | checkin
annotations |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"6775888470317a6d69121779b489bb2dc7350318" 6775888]:
{{{#!CommitTicketReference repository=""
revision="6775888470317a6d69121779b489bb2dc7350318"
[5.2.x] Fixed #36696 -- Fixed NameError when inspecting functions with
deferred annotations.
In Python 3.14, annotations are deferred by default, so we should not
assume that the names in them have been imported unconditionally.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36696#comment:8>
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/0107019a3a4f6b6b-9f8cc455-3771-4b00-8c46-1ef13690a952-000000%40eu-central-1.amazonses.com.
