5.0.1 Windows client

[javiere]

With the new client release 5.0.1. Don't display "DATE" information inside the History partner.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Javiere.

would you please attach the screenshot or the traceback if any error is shown?

We don't get this error at our end.

Thanks.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello,

So it happens sometimes? or everytime?

Specifically , when this 'bugnotok' appears on your screen?

Thanks.

[Anup(SerpentCS) (anup-serpent)]

Yes, its an issue with pytz.(i.e. when there is non-null timezone assigned to any user,its creating problems).

[GEM (nimp3)]

problem seems to be solved with v5.0.6
can you confirm

[GEM (nimp3)]

i WANTED TO SAY i HAVE NO PROBLEM WITH PYTZ NOW

[Olivier Dony (Odoo) (odo-openerp)]

I think this bug (and at least some of those marked as duplicates of it) are all dupes of the fundamental issue with the use of time.tzname to get the server timezone (#389544), which is not reliable and causes all these issues.

This is the main thing that needs fixing.

BTW, several workarounds have been identified already, if you need a temporary solution (see the comments on the dupes):
 * unset the user's timezone in OpenERP so that the server timezone is not used
 * ugly: patch your python time module to add the unsupported timezone needed by your system, and copy the timezone data
 * ugly: hardcode a valid timezone in the server code instead of using time.tzname

[Olivier Dony (Odoo) (odo-openerp)]

I updated the duplicates to reflect that all of this stems from #389544.