#25846 closed Uncategorized (needsinfo)
RemovedInDjango110Warning coming from SubfieldBase
Reported by: | Yuval Adam | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.9 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (7)
comment:1 by , 9 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
comment:2 by , 9 years ago
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.
comment:3 by , 9 years ago
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
comment:4 by , 9 years ago
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!
comment:7 by , 9 years ago
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.
And?