- Mailing Lists
- Contributors
- 17.0 branches
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Ledger for the individual related to a company
Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
17.0 branches
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:
- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
by Stéphane Bidoul - 04:18 - 12 Nov 2023
Follow-Ups
-
Re: 17.0 branches
Thanks a lot Stéphane for all these evolutions.Some of them have a really good impact on the environment, double thanks for that.Le lun. 13 nov. 2023 à 15:52, Juan José Scarafía <notifications@odoo-community.org> a écrit :El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 07:25 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan José Scarafía - 03:51 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
It can be decided per branch answering the copier question.Regards.
by Pedro M. Baeza - 03:36 - 13 Nov 2023 -
Re: 17.0 branches
Will Ruff also be used on earlier branches or will it only be used for 17.0+?Il giorno dom 12 nov 2023 alle ore 17:25 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 03:31 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
-
Re: 17.0 branches
Thanks StéphaneOn Sun, Nov 12, 2023 at 7:55 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Hi everyone,
The 17.0 branches are being created in all OCA repos as I'm writing this.
There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:- It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
- The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
- pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
- pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.In case of problem, let us know of any problem by creating an issue in the repo template project [3]Best regards,[1] https://docs.astral.sh/ruff/rules/_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Mostafa Barmshory - 03:28 - 13 Nov 2023 - It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.