#28752: Prevent django.setup() from running multiple times
-------------------------------------+-------------------------------------
Reporter: pascal chambon | Owner: pascal
Type: | chambon
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
Comment:
OK, sorry, having looked again at this, I just can't see that the extra
code in `django.setup()` merits the change.
TBH in 10+ years of using Django I've never seen an actual issue here.
Maybe `py.test` runs into them, but it seems to me that it would be easy
enough to put required locking code outside of the `setup()` in whatever
bootstrap script is in play.
As it is, `setup()` is simple and straight-forward. With the proposed
changes it's anything but. Given that, and the lack of consensus as
whether, and even why, we should address this, I'm going to say `wontfix`.
On assessment I think addressing this is putting the cart before the
horse.
--
Ticket URL: <https://code.djangoproject.com/ticket/28752#comment:23>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/063.37f532a8307d04c35543d7cdbdc373c1%40djangoproject.com.
