c2c-oerpscenario team mailing list archive

[Serpent Consulting Services <644267@xxxxxxxxxxxxxxxxxx>]

The Patch provided by Joel has been(not the complete patch, but the bug
actually gets fixed) applied by Olivier dony at
https://bugs.launchpad.net/openobject-server/+bug/673773 in version 5 as
well.

Faced a similar one while my local code was not updated, pulling the code made me sure that it has been fixed by revisions:
http://bazaar.launchpad.net/~openerp/openobject-server/5.0/revision/2111 AND
http://bazaar.launchpad.net/~openerp/openobject-server/5.0/revision/2144

Hence, this bug should end as released (keeping in mind the fact that
the version 5.0.16 has been released by revision 2173 -
http://bazaar.launchpad.net/~openerp/openobject-server/5.0/revision/2173
)

Thanks,
Serpent Consulting Services.



** Changed in: openobject-server
       Status: In Progress => Fix Released

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

Title:
  [5.0.14] safe_eval() incompatible with python2.7's bytecode

Status in OpenERP Server:
  Fix Released

Bug description:
  openerp-server 5.0.14 when run on python 2.7 is basically useless
  (when using addons), due to the changes in low-level python 2.7
  opcodes. The safe_eval() function in bin/tools/safe_eval.py doesn't
  expect the new opcodes and fails on virtually every operation. The
  attached patch adds the four missing py2.7 opcodes to safe_eval and
  fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/644267/+subscriptions