not necessarily wrong, just a different timezone. If you're going to display "prettydates" just in the browser for a "nicer visualization" you should take into consideration that your server's locatime can be different from the users's browser one.
In a "perfect" setup, your server is on GMT (that is, utc), your app uses request.utcnow in all the places instead of request.now (and datetime.datetime.utcnow() instead of datetime.datetime.utcnow()). You'll have prettydate working right. On Wednesday, October 10, 2012 10:38:32 AM UTC+2, David Sorrentino wrote: > > Hey Niphlod, > > Thank you for your help. > > The version is 2.0.9 (2012-10-05 09:01:45) dev > > I tried datetime.datetime.now() in my application and I just discovered > that it is 2 hours late. This explains why prettydate is then 2 hours in > hurry! > The odd thing is that if I open a python console and try > datetime.datetime.now(), I get the right time. O_O > > Something wrong with my server? > > Cheers, > David > > > On 10 October 2012 10:28, Niphlod <nip...@gmail.com <javascript:>> wrote: > >> should calculate the difference between datetime.datetime.now() and your >> date. what web2py version are you using ? >> >> >> On Wednesday, October 10, 2012 10:16:24 AM UTC+2, David Sorrentino wrote: >>> >>> Hello everybody, >>> >>> I am using the module *prettydate*, but it seems that it matches the >>> datetime I give as input with a wrong timezone. >>> >>> For example now it's 10:12 am at my place. >>> >>> This is the datetime I give as input: 2012-10-10 10:12:00. >>> >>> This is the code: >>> >>> from gluon.tools import prettydate >>>> pretty_d = prettydate(input_datetime, T) >>>> >>> >>> >>> And this is the result: "2 hours from now". >>> It's 2 hours in hurry!! :) >>> >>> Am I wrong in something? >>> >>> I wish you a wonderful Wednesday, >>> David >>> >>> >>> -- >> >> >> >> > > --
