Dear python and odoo community,
What standards / conventions / guidelines do you follow to write beautiful, clean and durable code? Also, how do you make sure that everyone follows them? It can be set as a rule, but how do you ensure that it's respected by all?
I know many people don't see the benefit of a  pythonic code, but working with teams and people from different backgrounds and cultures, I always find it's necessary to have some "ground rules" to ensure quality and results, since trying to decrypt a malformed code can be quite frustrating and time consuming
Odoo is the world's easiest all-in-one management software.
 It includes hundreds of business apps:
- CRM
- e-Commerce
- Accounting
- Inventory
- PoS
- Project
- MRP
This question has been flagged
Hi,
Odoo has own code guiedlines: https://www.odoo.com/documentation/12.0/reference/guidelines.html. It is reasonable to follow them, plus PEP8 - https://www.python.org/dev/peps/pep-0008/.
Controlling is a sort of complex issue. I guess, here are 2 main ways (to combine):
- Automatic tests and, ideally, implemented system of continuous deployment (https://en.wikipedia.org/wiki/Continuous_deployment) 
- Carefully merge requests check for each commit (not all guidelines might be checked automatically) 
The process of introducing such changes would be painful :)
pep20, pep8, pep257 and odoo guidelines
Enjoying the discussion? Don't just read, join in!
Create an account today to enjoy exclusive features and engage with our awesome community!
Sign up| Related Posts | Replies | Views | Activity | |
|---|---|---|---|---|
|  | 2 Aug 25  | 3187 | ||
|  | 1 Jun 24  | 3051 | ||
|  | 3 Feb 25  | 4589 | ||
|  | 0 May 24  | 46 | ||
|  | 1 Apr 24  | 4034 | 
 
                        
In my case field name will be....
For many2one:
user_id
for one2many:
user_ids
for many2many
user_ids
for boolean:
is_record
for char:
name
reference: https://learnopenerp.tumblr.com/