Django settings now passed in a dictionary

[GoogleCodeExporter]

I'm using the most recent revision of Django and django-pyodbc.

Django settings are now passed as a dictionary not the settings module itself.

What steps will reproduce the problem?
1. Upgrade to any revision of Django trunk after 10459
2. Try to run an app with some settings, like a TIME_ZONE.

What is the expected output? What do you see instead?
Get a type error complaining about the number of arguments. See attached
traceback.

Original issue reported on code.google.com by gaustin@gmail.com on 13 Jul 2009 at 6:46

Attachments:

• report.txt

[GoogleCodeExporter]

I fixed this myself. It's probably rough/unacceptable, as I've never really 
done this
before.

I couldn't get the test suite to run, so I didn't go and write/update those... 
Sorry.

Original comment by gaustin@gmail.com on 13 Jul 2009 at 7:44

Attachments:

• django-pyodbc-settings.diff

[GoogleCodeExporter]

Maybe I'm losing it... but I'm at revision 171 on my install and it didn't have 
these
changes. I looked at 151 and 157 and there seem to be similar changes there...

Will have to look into where I got this version of django-pyodbc...

Original comment by gaustin@gmail.com on 13 Jul 2009 at 10:00

[GoogleCodeExporter]

Disregard this issue. Not sure where things got confused...

Original comment by gaustin@gmail.com on 13 Jul 2009 at 10:18

[GoogleCodeExporter]

Closing, as per OP request. He was possibly using an old revision/mixed install 
of
django-pyodbc.

Original comment by cra...@gmail.com on 1 Aug 2009 at 4:06

• Changed state: Invalid