Hi Felix, >From what I know model and form DateField are completely TIME_ZONE agnostics.
This is not the case for DateTimeField however. Is this what you're using? Simon Le jeudi 24 septembre 2015 15:13:01 UTC-4, felix a écrit : > > El 23/09/15 17:12, felix escribió: > > > When today's date is entered in the form it shows a form error saying > that this date (today) is in the future. > What is wrong with the validator I'm using to allow dates until today? > > models.py > > ... > import datetime > > ... > > class SolicitudBase(models.Model): > .... > fecha = > models.DateField(validators=[MaxValueValidator(datetime.date.today(), > message="This date can't be in the future")]) > .... > > > I'm using Mysql and the following settings in my django project related to > timezone are commented: > > #TIME_ZONE = 'EST' > #USE_TZ = True > > My server (debian 7) is using US/Eastern timezone. > > and right now: > root@webapp:~# date > Wed Sep 23 17:04:36 EDT 2015 > > Thanks in advance, > Felix. > > > Thanks Simon for your suggestion. > I forgot to mention that it only happens with the present date (today) but > it doesn't happen with past dates. So it makes me think it could be a time > zone issue. > > Cheers, > Felix. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3dd66849-8d11-4233-8c3f-d1165a5bf2a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
