Thanks Bill, solved my puzzle. Reversion and debug-toolbar's latest version
are using old import.
And nkryptic, I tryed that, but the DepracationWarnings simply doens't turn
into errors with this command here =/
2013/1/7 nkryptic
> You could try running:
>
> $ python -W error manage.py runserve
You could try running:
$ python -W error manage.py runserver
That should cause the deprecation warning to actually raise an error and
cause a traceback to be displayed and hopefully show you where that import
is happening.
On Monday, January 7, 2013 1:13:33 PM UTC-5, Thiago wrote:
>
> Nope. If
This could be happening in some app that you have pip installed (or
equivalent) and
are using in installed apps, or which is being included by some app that is.
You could find-grep in your virtualenv's site-packages for 'default' and
pass the result
into grep 'urls', and if necessary, into grep '
Are you including any other apps that are not located under your project
folder?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/et1JsOmLoUQJ.
To post to t
Nope. If I grep my entire project folder with: grep "defaults" . -r, the
only result is:
Binary file ./settings.pyc matches
Then I delete it, and runserver again, I get the message:
/virtualenvs/env-hrp-rc/local/lib/python2.7/site-packages/django/conf/urls/defaults.py:3:
DeprecationWarning: django
In your urls.py file, you probably have something like:
from django.conf.urls.defaults import patterns, url, include
change that to:
from django.conf.urls import patterns, url, include
On Sunday, January 6, 2013 9:57:25 AM UTC-5, Thiago wrote:
>
> Hello,
>
> I am having this "DeprecationWarning:
6 matches
Mail list logo