#36956: import_string logic for AttributeError is too broad, can be improved
under
Python 3.10+
--------------------------------------+------------------------------------
Reporter: Glenn Matthews | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: 6.0
Severity: Normal | Resolution:
Keywords: import_string | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Sriniketh99):
Hi! I’d like to work on this ticket.
I’m currently learning more about Django internals, and this seems like a
good opportunity to understand import_string better. I’ll begin by
reviewing the current implementation and reproducing the behavior under
Python 3.10+, then work on refining the AttributeError handling as
proposed and submit a PR.
Please let me know if there are any additional considerations I should
keep in mind.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/36956#comment:2>
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/0107019ca29ea3b5-ddff01ca-0329-4888-bef8-cb4a74832887-000000%40eu-central-1.amazonses.com.
