Community mailing list archives

Re: Use of new odoo API when porting OCA addons

Akretion, Raphael Valyi
- 08/12/2014 02:32:57
Hello Nicolas,

I personally vote "NO, it shouldn't be a prerequisite for porting to v8" but I'll happily conform to voted decision.

justification: "the perfect is the enemy of the good". While we do brain masturbation with PEP-8 and other style details, 70% of the code that run in production is official OpenERP core that has really much lower coding standards (no PEP-8, mixed API...). So IMHO there is no point in loosing too much energy making our surface patch modules perfect when 70% of the running code remains with much lower coding standards. As we have limited resources to invest, I think we should always encourage doing better, even much better, but without going into some kind of what would be equivalent to "premature optimization" but of the code style.

Now, I heard from OpenERP SA that they planned to migrate all the official addons until v9 and even remove old API at v9. I'm in favor in encouraging API migration in OCA to make sure we follow and even precede that move, but without putting too much brutal burden to our fellow contributors in the meanwhile. 

My 0.02 R$

On Tue, Aug 12, 2014 at 3:19 AM, Nicolas Bessi <> wrote:
Dear community,

In order to avoid multiple sterile debate on Github and unilateral commits,
community should define a new guideline about the usage of new API.
Should it be a prerequisite when proposing addons port or new addons on OCA project for v8 and above?

It would be nice if OCA board can organize a poll on this topic.

My two cents


Nicolas Bessi
Senior ERP consultant
Business Solution technical manager

Camptocamp SA
CH-1015 Lausanne

Post to:

Raphaël Valyi
Founder and consultant
+55 21 3942-2434