#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:"953d31028a48911777d932e3ea76bedb2daf6ad8" 953d310]:
{{{#!CommitTicketReference repository=""
revision="953d31028a48911777d932e3ea76bedb2daf6ad8"
[6.0.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.
Backport of 601914722956cc41f1f2c53972d669ddee6ffc04 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36696#comment:7>
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/0107019a3a4d3ffc-550da363-3229-421f-9236-617c65c68c8b-000000%40eu-central-1.amazonses.com.
