#36716: Debugging can get stuck in an infinite loop if a setting is contained in
itself
-------------------------------------+-------------------------------------
Reporter: Willem Van Onsem | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 5.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: => wontfix
* status: new => closed
* type: Uncategorized => Cleanup/optimization
Comment:
Hello Willem, thank you for taking the time to report this. I understand
the situation you are describing. However, this kind of infinite recursion
can occur in many parts of Python when language features are used in
unintended ways. Since this only affects the local development environment
(since debug is on, which is not intended for production use), I think the
impact is limited and can be resolved locally during development. It does
not seem worth adding extra complexity or overhead to Django’s settings
handling to guard against such rare misuse cases.
--
Ticket URL: <https://code.djangoproject.com/ticket/36716#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/0107019a5e6f17d7-49254a3a-f9b7-498c-bdba-c0dd59ef6f58-000000%40eu-central-1.amazonses.com.
