id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 14264,settings.configure has undocumented differences from using a settings module,Carl Meyer,Gary Wilson,"Calling django.conf.settings.configure bypasses the Settings class in that module entirely (in favor of UserSettingsHolder), thereby bypassing all of Settings.__init__. This makes it subtly but occasionally critically different: globs in INSTALLED_APPS are not processed, the os.environ timezone is not set, and there is no friendly string-conversion-to-tuple for settings like TEMPLATE_DIRS. Not setting os.environ timezone is [http://docs.djangoproject.com/en/1.1/topics/settings/#django.conf.settings.configure documented] and correct: settings.configure implies that you are in control of your environment and may be using Django as a piece of a larger system, Django should not go messing with the environment. The other two differences are oversights and should be fixed.",Bug,closed,Core (Other),dev,Normal,fixed,,metzen@…,Accepted,1,0,0,1,0,0