# Proposal create project coding standard for tryton

**URL:** <https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295>\
**Category:** Organisation\
**Tags:** project\
**Created:** [February 5, 2020, 4:36pm UTC](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295 "2020-02-05T16:36:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\
**Post date:** [February 5, 2020, 5:11pm UTC](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295/3 "2020-02-05T17:11:53Z")

</div>

> [@dvdmgl](#):
>
> improves code consistence and readability

This points have very few to do with the coding style.  
The key points are: good naming and proper design. And they are not and cannot be managed by tools.

> [@dvdmgl](#):
>
> avoids annoying editor warnings,

Well that depends on everyone editors.

> [@dvdmgl](#):
>
> avoids _nagging about formatting_

As I’m doing most of the reviewing, I have very little comment about format. And most of the time reviewbot has already commented.

> [@dvdmgl](#):
>
> “ _save time and mental energy for more important matters_ ”

Indeed I find that the formatting comes automatically out of a well though design. And usually bad code has bad design (even if it was linted or whatever).

> [@dvdmgl](#):
>
> pylint is a tools that helps preventing certain type of bugs bugs, suggesting improvements

We have already flake8 run by reviewbot. I do not think we must change but [improve it](https://bugs.tryton.org/issue7213).

> [@dvdmgl](#):
>
> helps current developers and to board in new developers

I do not see how if they have to setup more tools in order to start.

> [@dvdmgl](#):
>
> applying black, pylint will create possible merge and rebase issues for existing banches

Indeed it is more about backport of fixes. But it would be a major problem.

> [@dvdmgl](#):
>
> as of python 3.5 was introduced [type hints](https://docs.python.org/3.5/library/typing.html) would be helpful to introduce on core libs

I already though about that but I could not find a way to deal with dynamic class generation Tryton has.  
Maybe with a hook that create stub files automatically out of all the modules.  
But anyway, this is off topic about code style.

---

_[View the full topic](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295)._