#25070: Provide better (source) context with Django's warnings
------------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.8
Severity: Normal | Resolution:
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 timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I guess this is limited to module level imports. I'm not sure if your
proposal is feasible, but Python seems to use the same strategy for
deprecating modules (e.g. `Lib/imp.py`) and so suffers from the same
issue. I guess it would be interesting to see if there have been any
complaints there and any ideas or work on the issue. It seems like fixing
the problem upstream would yield the greatest benefit.
--
Ticket URL: <https://code.djangoproject.com/ticket/25070#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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.f3278d25cf1541805a21f70c02301b11%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
