-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hugo <[EMAIL PROTECTED]> wrote: > > >Attached is a patch against current svn (applies to 0.90 also), that > >automatically sets TIME_ZONE and LANGUAGE_CODE according to the >hosting > >system. > > Actually setting TIME_ZONE and LANGUAGE_CODE to the settings according > to the hosting system isn't "the right thing" in days where people buy > cheapest hosting all over the world. Don't think a west-coaster would > be happy with the timezone of the east coast ;-) > > So this can only be something optional, because there are people who > most definitely want to change it on per-project basis. For example my > IRC logger runs with Django Central Time, as it should be in sync (in > it's listings) with the Django Trac timeline and SVN changelogs. But > the machine is still my own machine running Europe/Berlin and > LANGUAGE_CODE de.
It's still entirely optional, it just gets set to the hosting defaults when you use: django-admin.py startproject blah so that the settings.py file is (potentially) correct for most people, it doesn't in any way, shape, or form change the ability to edit settings.py. Have you got a different suggestion for how this should be set? Maybe it would be good to be able to give a whole metric full of options to the django-admin.py utility? Thoughts? Cheers, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDghd2Eh8oWxevnjQRArcDAJ0dIZE4S47gHP2ajhrvk0hNEjESqwCglRCH +ZXdxAzsZ7MGMx3Zp/+WAEs= =g3qo -----END PGP SIGNATURE-----
