Ask Your Question
0

DeprecationWarning(s)

asked 2011-12-13 06:16:26 -0500

drpoovilleorg gravatar image

updated 2011-12-13 06:45:04 -0500

Evgeny gravatar image

Just wanted to point out some Deprecation warnings i'm seeing in the logs that i didn't see anyone else point out yet. I suppose these are 'known issues' already?

[Tue Dec 13 06:12:39 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.'

[Tue Dec 13 06:12:39 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:41 2011] [error] /usr/lib/python2.6/site-packages/django/contrib/auth/models.py:393: DeprecationWarning: The user messaging API is deprecated. Please update your code to use the new messages framework.
[Tue Dec 13 06:12:41 2011] [error]   category=DeprecationWarning)

[Tue Dec 13 06:12:41 2011] [error] /usr/lib/python2.6/site-packages/django/core/context_processors.py:27: DeprecationWarning: The context processor at `django.core.context_processors.auth` is deprecated; use the path `django.contrib.auth.context_processors.auth` instead.

[Tue Dec 13 06:12:41 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:42 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead.

[Tue Dec 13 06:12:42 2011] [error]   DeprecationWarning
[Tue Dec 13 06:12:42 2011] [error] /usr/lib/python2.6/site-packages/django/db/__init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.'
edit retag flag offensive close merge delete

Comments

These are not bugs :) but only warnings. That means that in the future versions of Django those features will turn into bugs, possibly in Django 1.4

Evgeny gravatar imageEvgeny ( 2011-12-13 06:44:26 -0500 )edit
2

I've asked our designer to fix the layout issue with the preformatted text flowing over the author info.

Evgeny gravatar imageEvgeny ( 2011-12-13 07:05:31 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2011-12-13 06:40:25 -0500

Hi, this warning is raised by django > 1.2 the django default settings for databases used to be the one that we still use, if you want to remove this warning just change your settings database format to the new one explained here: https://docs.djangoproject.com/en/dev/ref/settings/#databases

edit flag offensive delete link more

Comments

with django 1.3 (what we use), a few new deprecation warnings appear: Authentication backends without asupportsanonymoususerattribute are deprecated., and Authentication backends without asupportsobjectpermissionsattribute are deprecated.

piskvorky gravatar imagepiskvorky ( 2011-12-13 13:57:36 -0500 )edit

Hmm, I thought markdown strings between backticks `` were not formatted.

piskvorky gravatar imagepiskvorky ( 2011-12-13 14:00:26 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2011-12-13 06:16:26 -0500

Seen: 905 times

Last updated: Dec 13 '11