Ticket #1002 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Server and Django 1.2

Reported by: Owned by: desai
Priority: minor Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-reports Version: 1.0
Keywords: Cc:


I've noticed that both the bcfg2 server and bcfg2-admin report DeprecationWarnings? when invoked on systems with versions of Django including and newer than Django 1.2:

For example, on my RHEL5 system with Django 1.3:

# bcfg2-admin reports validate /usr/lib/python2.4/site-packages/django/db/ DeprecationWarning?: settings.DATABASE_* is deprecated; use settings.DATABASES instead.


/usr/lib/python2.4/site-packages/django/db/ DeprecationWarning?: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.'


0 errors found

I see in bcfg2/src/lib/Server/Reports/ that it uses DATABASE_ENGINE, DATABASE_NAME, etc., and that API has been deprecated, according to the Django docs: "Prior to Django 1.2, Django used a number of settings to control access to a single database. Django 1.2 introduces support for multiple databases, and as a result the way you define database settings has changed.

Any existing Django settings file will continue to work as expected until Django 1.4. Until then, old-style database settings will be automatically translated to the new-style format."


Change History

comment:1 Changed 12 years ago by laszlo

  • Status changed from new to closed
  • Resolution set to fixed

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.