Repository navigation
Conversation
(lp:c2c-addons/6.1 rev 11)
(lp:c2c-addons/6.1 rev 11.1.4)
(lp:c2c-addons/6.1 rev 28.1.1)
…t is the blessed target. (lp:c2c-addons/6.1 rev 40.2.1)
(lp:c2c-addons/6.1 rev 45.1.4)
…TK client, because for 6.1 the web client is the blessed target. (lp:c2c-addons/6.1 rev 116)
This fixes OCA/server-tools#125 because in some Ubuntu systems lsb_release outputs to stderr as well as stdout. This message will be printed to console, not logged nor shown among server infomation. That way the message is lost and only pollutes unit tests output.
In order to get visibility on https://www.odoo.com/apps the OCA board has decided to add the OCA as author of all the addons maintained as part of the association.
nice with static files
* [IMP] load server environment options from odoo rcfile This allows delivering the code with default configuration options for all environments in the server_environment_file module, but letting the administrator override some configuration entries in the regular odoo configuration file. * server_environment_file: update README
To trigger rebuild following change in setup.py
6b87bcb to
de83b9e
Compare
Assisted-by: Claude Opus 5.5
Assisted-by: Claude Opus 5.5
de83b9e to
efdd250
Compare
Assisted-by: Claude Opus 5.5
From Python 3.14 on, partialmethod is constructed in __new__ instead of __init__, so overriding __init__ to pop a __name__ keyword raises a TypeError. Don't override the constructor: set __name__ on the instance after creating it. Assisted-by: Claude Opus 5.5
bf7f4b1 to
f04f6f0
Compare
|
@jgrandguillaume @sbidoul @pedrobaeza I'm reaching to you regarding the issue I ran up when migrating this module to v20 I don't know if you are the right people for this question, otherwise forward it to who it belongs to. |
|
The CI runs in the same Python version as Odoo runs its runbot, as it's fixed to just that version. I recommend you to use that version as well, or you'll find troubles like the mentioned one, but not only with OCA, but with Odoo core itself. The same applies to the versions of the Python libraries. |
|
@pedrobaeza I don't fully agree with this remark. https://github.com/odoo/odoo/blob/20.0/odoo/release.py#L39C1-L40C25 MIN_PY_VERSION = (3, 12) So the modules should work on 3.12, 3.13 and 3.14 |
|
Yes, theoretically, but with nobody testing that, you shouldn't risk. As said, Odoo core is not being tested in another Python version. I don't think the benefits (which ones?) of using Python 3.14 will worth the possible problems. |
Odoo is using 3.14 on Ubuntu 26.04 LTS in there CI pipelines
|
|
Well, here it is an interesting point... Well, when we set the version of python to use, we usually set the minor version provided by odoo. At some points we discussed if we should increase the number of versions tested, however, if we increase the number of CIs, it will be slower and we could achieve the limits of concurrent CI more often. This kind of problems are not usual and maybe it should have sense to have that in some specific repos, like this one, server repositories, rest-framework connector or queue_job 🤔 |
Standard migration to 20.0, plus two fixes for 20.0 ORM changes in dynamically added fields:
server.config: register the generated fields with__set_name__(20.0 requires_module).server.env.mixin: add the generated*_env_default/*_env_is_editablefields to_fields_update_order__.Also:
ir.access.csv,webadded todepends(tests useForm), ruff fixes.Changes reviewed and tested by me.
Assisted-by: Claude Opus 5.5