Btw, Django 1.1.4 is in EPEL4.
On Tue, Aug 2, 2011 at 2:21 PM, Jörgen Maas <[email protected]> wrote: > I finally found it: > > Changed in Django 1.1.2: None was added as an allowed value > > Grtz, > Jorgen Maas > > On Tue, Aug 2, 2011 at 1:58 PM, James Cammarata <[email protected]> wrote: >> Perhaps they fixed this in 1.1.4? I can't reproduce it now on my home >> system. I'll check on my work system today, but that was definitely >> the issue at the time. >> >> On Tue, Aug 2, 2011 at 1:54 AM, Jörgen Maas <[email protected]> wrote: >>> <snip> >>>> >>>> commit 257ef06364e224bc2af9edafb28449b0d2784521 >>>> Author: James Cammarata <[email protected]> >>>> Date: Thu Jun 30 17:19:47 2011 -0500 >>>> >>>> Setting TIME_ZONE to None in web/settings.py causes a 500 error on a >>>> RHEL5 system with python 2.4 and django 1.1. Commenting out the config >>>> line has the same effect as setting it to None, and prevents the 500. >>>> >>> >>> With this patch applied django produces wrong time information on CentOS5. >>> Setting it to None restores proper behaviour on CentOS5, with Django >>> 1.1.4 from EPEL5 >>> >>> Are you sure the 500 was a direct result of the TIME_ZONE settings?? >>> _______________________________________________ >>> cobbler-devel mailing list >>> [email protected] >>> https://fedorahosted.org/mailman/listinfo/cobbler-devel >>> >> _______________________________________________ >> cobbler-devel mailing list >> [email protected] >> https://fedorahosted.org/mailman/listinfo/cobbler-devel >> > _______________________________________________ cobbler-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler-devel
