#19636: inhibit signals to modify some field on tests
-----------------------------------+--------------------------------------
Reporter: oscaracena@… | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: 1.4
Severity: Normal | Resolution: wontfix
Keywords: signals, tests | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by carljm):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Thanks for the suggestion! I can see that there are some cases where this
would be useful; I also think it would invite abuse. In most cases I think
this is better handled by making the signal handler smarter (or not using
a signal at all). And regardless, this decorator can easily live outside
of Django core, I don't think it's a sufficiently common pattern to
warrant inclusion in core.
--
Ticket URL: <https://code.djangoproject.com/ticket/19636#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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
