Doing this is usually a bad practice, because you break the encapsulation principles, and lose the assumption that the original module will still work as it is supposed to. You definitely do NOT want to override the unit tests of the original module.
What you could do, is to drop the "required" attribute on the field itself, and instead put it on the field in your inherited view(s), to achieve the same effect without breaking the original module. ------------------------ Olivier Dony OpenERP/Tiny Belgium -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=48539#48539 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
