On 04/23/2012 10:45 AM, Georges Racinet wrote:
Le 23/04/2012 09:38, Olivier Dony a écrit :
You should never touch the MRO to alter OpenERP models inheritance, or at all.
This is a Python implementation detail and the ORM takes care of managing it
properly when you use OpenERP inheritance. If you need to mess with it your
design is probably bad and certainly too complicated.
+1 too. However, sometimes the design of the *official* addons is such
that skipping through the MRO is the most elegant solution. My example
was taken from a small glue module that makes project_timesheet work
with analytic_user_function...
Cheers,
Stefan.
--
Therp - Maatwerk in open ontwikkeling
Stefan Rijnhart - Ontwerp en implementatie
mail: [email protected]
tel: +31 (0) 614478606
http://therp.nl
https://twitter.com/therp_stefan
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
