It is not. datetime.now() will return now in UTC which is always now in
any timezone.
I think is not true. datetime.now() return current local date and time, not
UTC (1).
Tryton switched for 3.2 to good practice which is to
always work/store/manipulate UTC.
So adding a Date.now() that
2014-03-20 8:55 GMT+01:00 Raimon Esteve rest...@zikzakmedia.com:
It is not. datetime.now() will return now in UTC which is always now in
any timezone.
I think is not true. datetime.now() return current local date and time,
not UTC (1).
trytond force UTC. Ok, datetime.now() return UTC in
Will 3.2 release be Python 3 compatible?
On 19 Mar 18:44, andrey.sho...@gmail.com wrote:
Will 3.2 release be Python 3 compatible?
No http://hg.tryton.org/trytond/file/e0fa0ce19d7a/setup.py#l67
--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
pgpnaWmhSz2nJ.pgp
On 19 Mar 21:39, oscar wrote:
Is possible that this codereview enter in 3.2?
http://codereview.tryton.org/4141002/
Sorry but no, it is too late and there are still concerns about the
design.
--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: