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 <tevans...@googlemail.com> wrote:
> On Wed, Feb 29, 2012 at 3:33 PM, furby <jasonno...@gmail.com> 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.
>
> Customer is always right. Plus, job for life ;)
>
>
>
> > Here's the urlconf. I've literally commented out every urlpattern
> > expect the top one on line 4. Still breaks:
>
> > 1 from django.conf.urls.defaults import *
> > 2 from permitprint.app.models import *
> > 3 urlpatterns = patterns('django.views.generic.simple',
> > 4 (r'^/?$', 'direct_to_template', {'template': 'index.html'}),
> > 5 """
>
> Hmmpf. One of the things improved since 0.96 is that error reporting
> of this kind has improved. There is an import error coming from one of
> the imports in the urlconf, and that is why it cannot import the
> urlconf. Is there any date handling code in the top level of the
> permitprint.app.models?
>
> Cheers
>
> Tom
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
