#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 ptone):
If I have to pick between siding with what is in the best interest of
Django Users, or Python core, I'm going to bias slightly toward the users.
I had also considered using a different warning class - but I think we are
actually using DeprecationWarning exactly as intended - and really the
decision is the same as changing the filters, just getting there via
another route. It seems pretty clear that Django is a developer tool -
not end user software. The end users are web users and aren't exposed to
warnings.
http://docs.python.org/dev/whatsnew/2.7.html#the-future-for-python-2-x
Reenabling warning output is suggested as an option in the above docs - so
I'm not sure why it is considered anti-python (Alex to this position on
IRC) to choose to display warnings in a context where it makes sense (a
Django development environment).
Another option is to just enable the deprecation warning output inside the
runserver command - as we make clear this is a dev server.
--
Ticket URL: <https://code.djangoproject.com/ticket/18985#comment:10>
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.
