furby wrote:
> Caught it. Haha. What a funny bug. From models.py:
>
> 196 d = dt.datetime.today()
> 197 expires = d.replace(year=d.year+1)
>
> There is no Feb. 29th, 2013. So this breaks. Thx for the help!
>
> On Feb 29, 9:50 am, Tom Evans wrote:
>> On Wed, Feb 29, 2012 at 3:33 PM, furby
use something like >>> d + datetime.timedelta(days=365)
http://docs.python.org/library/datetime.html#timedelta-objects
Cheers,
AT
On Wed, Feb 29, 2012 at 12:59 PM, furby wrote:
> Caught it. Haha. What a funny bug. From models.py:
>
> 196 d = dt.datetime.today()
> 197 expires = d.replace(ye
Caught it. Haha. What a funny bug. From models.py:
196 d = dt.datetime.today()
197 expires = d.replace(year=d.year+1)
There is no Feb. 29th, 2013. So this breaks. Thx for the help!
On Feb 29, 9:50 am, Tom Evans wrote:
> On Wed, Feb 29, 2012 at 3:33 PM, furby wrote:
> > The guy I built thi
On Wed, Feb 29, 2012 at 3:33 PM, furby wrote:
> The guy I built this for does not want to pay me to maintain it, so
> it's still on .96. And yet when something breaks randomly he wonders
> why. Debug enabled today for debugging. There is no dev
> environment. Only production for this.
Custome
o is breaking randomly today due to the
> > extra leap year day. Any help on this would be appreciated. I can't
> > track it down.
>
> > Traceback (most recent call last):
> > File "/home/nolenjb/django/django_src/django/core/handlers/base.py" in
> >
f_module.urlpatterns:
> File "/home/nolenjb/django/django_src/django/core/urlresolvers.py" in
> _get_urlconf_module
> 180. raise ImproperlyConfigured, "Error while importing URLconf %r:
> %s" % (self.urlconf_name, e)
>
> ImproperlyConfigured at /admin/
>
in
_get_urlconf_module
180. raise ImproperlyConfigured, "Error while importing URLconf %r:
%s" % (self.urlconf_name, e)
ImproperlyConfigured at /admin/
Error while importing URLconf 'permitprint.urls': day is out of
range for month
--
You received this message because you ar
7 matches
Mail list logo
