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
Deze vraag is gerapporteerd
3
Antwoorden
9889
Weergaven
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
Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!
Maak vandaag nog een account aan om te profiteren van exclusieve functies en deel uit te maken van onze geweldige community!
Aanmelden| Gerelateerde posts | Antwoorden | Weergaven | Activiteit | |
|---|---|---|---|---|
|
2
aug. 25
|
4637 | ||
|
1
jun. 24
|
4653 | ||
|
3
feb. 25
|
6460 | ||
|
0
mei 24
|
46 | ||
|
1
apr. 24
|
5942 |
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/