#26425: django/utils/six.py generates a RemovedInDjango110Warning
-------------------------------------+-------------------------------------
Reporter: mvanderlinde | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage:
runserver,SubfieldBase,RemovedInDjango110Warning| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by davidszotten):
* status: closed => new
* resolution: invalid =>
Comment:
seeing this from a few different 3rd party packages. if they are using
six.with_metaclass, the otherwise helpful indication of what caused there
warning is pretty useless
i guess it's possible to try to detect six, though an easier workaround
might be to bump the stacklevel, and err on the side of going too far,
which might at least find an import statement indicating where to look
thoughts?
--
Ticket URL: <https://code.djangoproject.com/ticket/26425#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.b5e949ab73928faaa47c435ccb891e97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
