{{{
/usr/local/lib/python2.7/dist-packages/django/utils/hashcompat.py:9:
DeprecationWarning: django.utils.hashcompat is deprecated; use hashlib
instead DeprecationWarning)
}}}
When I updated to 1.5.1 I expected that this'd have been fixed, but it
isn't.
I'm not using this library directly in my code, so I guess there is/are
some old deprecated imports in Django that should be changed.
P.S. I'm using the following 3rd party apps: 'captcha', 'gravatar',
'transmeta', 'south', 'wysihtml5'
--
Ticket URL: <https://code.djangoproject.com/ticket/20475>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Looking at
[http://ci.djangoproject.com/job/Django%201.5/database=sqlite3,python=python2.7/lastBuild/console
the latest CI build] of the 1.5.x branch it looks like this warning is not
raised.
I guess one of your 3rd party apps is using the deprecated
`django.utils.hashcompat` module.
To track down which one is the culprit you should try running your
testsuite or your development server (or a command that triggers this
warning) while setting python warning control to the error level and study
the traceback: e.g. `python -Werror ./manage.py runserver`. This should
point you to module referencing `django.utils.hashcompat`.
You can then notify the author or the app of this issue and even write a
patch to get rid of this pesky warning.
--
Ticket URL: <https://code.djangoproject.com/ticket/20475#comment:1>
Comment (by sharkwang@…):
File "C:\Users\...\AppData\Roaming\Python\Python27\site-packages\django_py
odbc\creation.py", line 3, in <module>
from django.utils.hashcompat import md5_constructor
File "C:\Users\...\AppData\Roaming\Python\Python27\site-
packages\django\ut
ils\hashcompat.py", line 9, in <module>
DeprecationWarning)
DeprecationWarning: django.utils.hashcompat is deprecated; use hashlib
instead
--
Ticket URL: <https://code.djangoproject.com/ticket/20475#comment:2>
Comment (by mjtamlyn):
The warning is being raised by code in django-pyodbc. This is the package
which needs updating.
--
Ticket URL: <https://code.djangoproject.com/ticket/20475#comment:3>
Comment (by aaugustin):
Hence this isn't a bug in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/20475#comment:4>