Translation system not compatible with Babel 1.3 API
Bug #1226576 reported by
Stefan Rijnhart (Opener)
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Aeroo Reports |
Fix Committed
|
Undecided
|
Unassigned | ||
| Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Low
|
OpenERP's Framework R&D | ||
Bug Description
It seems Babel on Pypi moved from 0.9.6 to 1.3 recently (Pypi mentions 2013-07-29).
The update includes this change:
https:/
The API change causes the following error:
openerp.
Traceback (most recent call last):
File "[path]
keywords=
ValueError: too many values to unpack
As a result, translatable terms from the code are not exported using Babel 1.3.
-- edit --
I mentioned missing translations in the OpenERP pot files, but this was a false alarm.
Related branches
lp:~therp-nl/openobject-server/7.0-lp1226576-restore_babel_compatibility
- Olivier Dony (Odoo): Approve
-
Diff: 17 lines (+5/-2)1 file modifiedopenerp/tools/translate.py (+5/-2)
lp:~therp-nl/ocb-server/7.0-lp1226576-restore_babel_compatibility
- OpenERP Community Backports: Pending requested
-
Diff: 17 lines (+5/-2)1 file modifiedopenerp/tools/translate.py (+5/-2)
lp:~therp-nl/aeroo/7.0-lp1226576-restore_babel_compatibility
- Alistek developers - http://www.alistek.com: Pending requested
-
Diff: 17 lines (+5/-2)1 file modifiedreport_aeroo/translate.py (+5/-2)
| description: | updated |
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #1 |
| Changed in openobject-server: | |
| assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
| importance: | Undecided → Low |
| milestone: | none → 7.0 |
| status: | New → Confirmed |
| summary: |
- Missing code translations due to Babel API changes + Translation system not compatible with Babel 1.3 API |
Revision history for this message
| Stefan Rijnhart (Opener) (stefan-opener) wrote | #2 |
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #3 |
| Changed in openobject-server: | |
| status: | Confirmed → Fix Released |
Revision history for this message
| Stefan Rijnhart (Opener) (stefan-opener) wrote | #4 |
| no longer affects: | ocb-server/7.0 |
| no longer affects: | ocb-server |
Revision history for this message
| Stefan Rijnhart (Opener) (stefan-opener) wrote | #5 |
| Changed in aeroo: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Hello,
Thanks for reporting and for providing a patch! I'm not sure we can directly make a direct connection between missing translations in POT files and this babel API change, because at least for the core branches all terms extractions are manually done and never triggered this error. They may be slightly outdated however, in which case you should request a re-export (on stable series in which terms to translate seldom change, we only export new terms every few months)
We should however fix the extraction system to make it compatible with the new babel API, and ideally that should be done in a way that is compatible with both APIs.