c2c-oerpscenario team mailing list archive

Thread
Date

[Bug 490937] Re: code using datetime.strptime() from datetime crashes client under CentOS/RHEL 5/Python 2.4

To: c2c-oerpscenario@xxxxxxxxxxxxxxxxxxx
From: "tfr \(Openerp\)" <490937@xxxxxxxxxxxxxxxxxx>
Date: Thu, 23 Dec 2010 11:17:39 -0000
Reply-to: Bug 490937 <490937@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: openobject-client
     Assignee: (unassigned) => OpenERP sa GTK client R&D (openerp-dev-gtk)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/490937

Title:
  code using datetime.strptime() from datetime crashes client under CentOS/RHEL 5/Python 2.4

Status in OpenObject GTK Client:
  Triaged
Status in CentOS:
  New

Bug description:
  Since some 5.0.1+ version, widgets have been using default datetime for doing dates instead of mx.DateTime.

This leads to the following errors, crashing the client and even corrupting the database in some cases: 
 
AttributeError: type object 'datetime.datetime' has no attribute 'strptime'

Looking around in datetime.c it seems Python 2.4 does not have a strptime in datetime.

Either revert to mx.DateTime or drop compatibilty for Python 2.3+ (as referred to in the documentation). The latter would be severely dissapointing due to CentOS/RHEL 5 shipping with only Python 2.4.