code using datetime.strptime() from datetime crashes client under CentOS/RHEL 5/Python 2.4
Bug #490937 reported by
The Loeki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo GTK Client (MOVED TO GITHUB) |
Won't Fix
|
Undecided
|
OpenERP sa GTK client R&D | ||
| CentOS |
New
|
Undecided
|
Unassigned | ||
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.
| summary: |
- code use datetime strptime from DT break client under CentOS/RHEL - 5/Python 2.4 + code using datetime.strptime() from datetime crashes client under + CentOS/RHEL 5/Python 2.4 |
| Changed in openobject-client: | |
| status: | New → Triaged |
| Changed in openobject-client: | |
| assignee: | nobody → OpenERP sa GTK client R&D (openerp-dev-gtk) |
Revision history for this message
| tfr (Openerp) (tfr) wrote | #1 |
| Changed in openobject-client: | |
| status: | Triaged → Invalid |
| status: | Invalid → Won't Fix |
To post a comment you must log in.
The V6 of openerp is designed for python 2.5 and above, we won't fix bug related with python 2.4. And if the bug concern v5, please report the bug using your publisher warranty