Bug 1388447 Comment 32 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Mike Hommey [:glandium] from comment #28)
> The Linux builds on automation are using python 3.5. I think it's fair to maybe require a newer version for tests, but we should at least keep 3.5 for the build system.

Sounds good. The downside to using a different version for non-build things is that people might get used to using e.g f-strings and accidentally add one to a shared library that the build uses (e.g mozbase). Not a huge deal as it will get backed out, but could still be annoying.

Whether or not we standardize on a single Python version, we'll need to make sure the unittests for various modules are all running with the minimum.

(In reply to Mike Hommey [:glandium] from comment #28)
> Actually, neither is really acceptable downstream (especially the second) ; FWIW, distros with ongoing support do come with python 3.5.

Ubuntu 14.04 LTS (eol April 2022), seems to come with 3.4. By that logic shouldn't 3.4 be the minimum? Also 16.04 eol is 2024. Will the build system be stuck on 3.5 for another 5 years? If that's the case, then yeah.. maybe it would be better to use a more modern version for non-build things in the meantime.
(In reply to Mike Hommey [:glandium] from comment #28)
> The Linux builds on automation are using python 3.5. I think it's fair to maybe require a newer version for tests, but we should at least keep 3.5 for the build system.

Sounds good. The downside to using a different version for non-build things is that people might get used to using e.g f-strings and accidentally add one to a shared library that the build uses (e.g mozbase). Not a huge deal as it will get backed out, but could still be annoying.

Whether or not we standardize on a single Python version, we'll need to make sure the unittests for various modules are all running with the minimum version they need to support.

(In reply to Mike Hommey [:glandium] from comment #28)
> Actually, neither is really acceptable downstream (especially the second) ; FWIW, distros with ongoing support do come with python 3.5.

Ubuntu 14.04 LTS (eol April 2022), seems to come with 3.4. By that logic shouldn't 3.4 be the minimum? Also 16.04 eol is 2024. Will the build system be stuck on 3.5 for another 5 years? If that's the case, then yeah.. maybe it would be better to use a more modern version for non-build things in the meantime.

Back to Bug 1388447 Comment 32