Fix RemovedInDjango30Warning from Django 2.0+
See original GitHub issueThe latest pytest surfaces all deprecation warnings at the end of the test run, so I’m seeing this one hundreds of times on my app.
.../python3.6/site-packages/django/db/models/sql/compiler.py:997: RemovedInDjango30Warning: Remove the context parameter from HashidAutoField.from_db_value(). Support for it will be removed in Django 3.0.
RemovedInDjango30Warning,
Should be an easy fix with conditional versions of the function for django versions.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
django error cannot import name 'RemovedInDjango30Warning'
This is caused by conflicts in Django versions as seen here. ImportError: cannot import name 'RemovedInDjango30Warning'.
Read more >django error cannot import name 'RemovedInDjango30Warning'
Guys im fairly new to Django and I just started working on a personal project and decided that ill-use pycharm (i think its...
Read more >How to upgrade Django to a newer version
Before upgrading, it's a good idea to resolve any deprecation warnings raised by your project while using your current version of Django. Fixing...
Read more >django-picklefield - PyPI
Pickled object field for Django. ... Silenced RemovedInDjango30Warning warnings on Django 2.0+ (thanks to canarduck). Restructured project directories.
Read more >Bug 1102680 – VUL-0: CVE-2018-14574: python-Django ...
Bug 1102680 - (CVE-2018-14574) VUL-0: CVE-2018-14574: python-Django: Open redirect ... release notes Django 2.0.8 fixes a security issue and a bug in 2.0.7....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
How lost we are when our tools break. Thank you for the PR. Released in 2.1.4.
That is weird… I’m pretty sure I did a publish since I created the 2.1.3 tag in git, and that happens after a publish as I copy and paste the lines output by
python setup.py publish
. Perhaps there was an error from twine that I missed or something. Since it was a fix specifically for installing from github instead of pypi, I guess it doesn’t matter at all. Still, I’ll make sure I check pypi after a publish. Thanks.