#18985: DeprecationWarning no longer loud by default in Python 2.7+
------------------------------+------------------------------------
Reporter: dstufft | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by russellm):
@aaugustin - I agree with the broad principle that we shouldn't diverge
from Python, but in this case, it seems to undermine our broader strategy.
We specifically chose PendingDeprecationWarning and DeprecationWarning as
a 2 phase mechanism for slowly introducing change in a way that couldn't
be easily ignored; Python core policy seems to be undermining our
intentions in this case.
Another option: Can we introduce a new warning subclass that *isn't*
silenced by default? Reading the 2.7 release notes, it seems clear to me
that the intention from Python core is that DeprecationWarning is for a
different purpose to what we're using it; in which case, it would make
sense to introduce a new warning type that serves *our* purposes.
--
Ticket URL: <https://code.djangoproject.com/ticket/18985#comment:9>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
