[Django] #25846: RemovedInDjango110Warning coming from SubfieldBase
Django
----------------------------------------------+--------------------
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer (models, ORM) | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
This warning pops up on runserver/validate/migrate:
~/.virtualenvs/proj/lib/python3.4/site-
packages/django/db/models/fields/subclassing.py:22:
RemovedInDjango110Warning: SubfieldBase has been deprecated. Use
Field.from_db_value instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/25846>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
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 claudep):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
And?
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:1>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by aaugustin):
To expand a bit on Claude's technically correct answer -- this warning is
likely caused by your code or a third-party library you're using. Running
under `python -Werror` will tell you where this warning originates.
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:2>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by yuvadm):
I'm not any closer to understanding which third party package is throwing
this error:
{{{
$ python -Werror manage.py runserver
Failed to import the site module
Traceback (most recent call last):
File "~/.virtualenvs/proj/bin/../lib/python3.4/site.py", line 703, in
<module>
main()
File "~/.virtualenvs/proj/bin/../lib/python3.4/site.py", line 683, in
main
paths_in_sys = addsitepackages(paths_in_sys)
File "~/.virtualenvs/proj/bin/../lib/python3.4/site.py", line 282, in
addsitepackages
addsitedir(sitedir, known_paths)
File "~/.virtualenvs/proj/bin/../lib/python3.4/site.py", line 204, in
addsitedir
addpackage(sitedir, name, known_paths)
File "~/.virtualenvs/proj/bin/../lib/python3.4/site.py", line 165, in
addpackage
f = open(fullname, "rU")
DeprecationWarning: 'U' mode is deprecated
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:3>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by timgraham):
It's not a Django issue, please see
https://github.com/pypa/virtualenv/issues/555.
Please use the resources linked from
TicketClosingReasons/UseSupportChannels instead of this ticket tracker to
get help going forward. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:4>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tim Graham <timograham@…>):
In [changeset:"64200c14e0072ba0ffef86da46b2ea82fd1e019a" 64200c14]:
{{{
#!CommitTicketReference repository=""
revision="64200c14e0072ba0ffef86da46b2ea82fd1e019a"
[1.9.x] Refs #25846 -- Added stacklevel to SubfieldBase warning.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:5>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tim Graham <timograham@…>):
In [changeset:"e73406d165ce1a38b003f5ef687184ddb09291a6" e73406d1]:
{{{
#!CommitTicketReference repository=""
revision="e73406d165ce1a38b003f5ef687184ddb09291a6"
[1.8.x] Refs #25846 -- Added stacklevel to SubfieldBase warning.
Backport of 64200c14e0072ba0ffef86da46b2ea82fd1e019a from stable/1.9.x
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:6>
Django
Reporter: yuvadm | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by yuvadm):
Thanks for the fix! Sorry I wasn't any clearer when opening the ticket,
but the stacklevel fix makes lots of sense and can hopefully assist in
debugging in future scenarios.
--
Ticket URL: <https://code.djangoproject.com/ticket/25846#comment:7>