On Aug 20, 2011, at 10:04 AM, nick name wrote: > On Saturday, August 20, 2011 11:19:07 AM UTC-4, Jonathan Lundell wrote: > Yeah, it probably should have been utcnow. Nothing to stop you (or web2py, > for that matter) from setting request.utcnow, though. > > Yep, I am already doing that. It may differ by a millisecond or 100 from the > original request.time (which is used by some parts / plugins), and I would > rather that it was all the same (that is, have .now be derived from .utcnow). > > I am considering overwriting request.now with utc time to make sure that my > system is all consistently in utc (and take care to format properly on > display). Do you know if there's going to be a problem with that?
It might work OK. If you do that, be sure to do it as the very first thing in your models. request.now is used in the session logic, some of which runs before your model; I'm not sure what the implications of that might be.
