Contributors mailing list archives
Re: V14, python versionby
Acsone SA/NV, Stéphane Bidoul
Thanks for taking up the topic with Odoo SA Moises. In the reply from Olivier I quote: "But why should you care about this? For the OCA I can't imagine any other option than to support all the same Python versions that are supported by the matching Odoo version. Anything else would just cause issues for your users. Sorry about that ;-)"
So yeah, I still think testing on 3.6 is a must and testing one of the two jobs on 3.8 is the best we can reasonably do in the short term.
Here is how it looks like: https://github.com/OCA/mis-builder/pull/325/commits/f7dc0bff689dfe6d86d56947c4144fcf2d4b3a33
With that we can safely announce that OCA supports and tests 14.0 with py 3.6 and 3.8, and that 3.7 should work but we don't test it due to limited resources.
Does that sound reasonable?
On Fri, Oct 16, 2020 at 9:13 PM Moises Lopez <email@example.com> wrote:
Hello everyone,I liked to know the Odoo internal opinion before to reply this thread.Maybe you are interested of Olivier Dony answer too:Summary:- Currently, runbot is running py3.6 for all current LTS versions (12.0, 13.0, 14.0)- They are in R&D to run py3.6, py3.7 and py3.8 in runbot for Odoo-14.0 builds- Odoo.sh is using py3.8 for 14.0 but py3.6 for 12.0 and 13.0Checking the "Table of versions" (1)- py3.6 will be deprecated soon at 2021-12 (1y2mo)py3.7 requires ugly code to support something basic as unittests like David commented us.Python3.8 will be tested in runbot.odoo.com (someday R&D)Python3.8 is used in live production in CD/CI Odoo.shIt should ensure fixes over this version similar to (2)So, the python version in the intersection is py3.8If for OCA is too expensive to support py3.6, py3.7 & py3.8 for nowThen, Should we pinned the CI to py3.8?What do you think?Note: FYI in Vauxoo, we have decided to use py3.8in live production (CD) and CI for Odoo v14.0 too