#44735: Required python version
Open Date: 2022-05-31 12:29
Last Update: 2022-06-06 18:53
URL for this Ticket:
https://osdn.net//projects/freeciv/ticket/44735
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44735
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-06-06 18:53 Updated by: alienvalkyrie
* Resolution Update from None to Accepted
* Details Updated
Comment:
Reply To cazfi
Reply To alienvalkyrie
As for whether we should bump the minimum Python version requirement, you know you won't find me saying "no" to that any time soon
I sort of assume that we can even find a volunteer to do that change...
We can. Attached patch has a textual dependency on #43945.
This patch does not yet mention the future python-follows-meson policy – I figure we'll cross that bridge when we get there, i.e. after S3_2 branching.
It also does not attempt looking for an alternate python3.5 executable – doing so would likely have to happen in configure rather than autogen.sh anyway, which would complicate building from tarball without Python.
---------------------------------------------------------------------
Ticket Status:
Reporter: cazfi
Owner: alienvalkyrie
Type: Patches
Status: Open [Owner assigned]
Priority: 5 - Medium
MileStone: 3.2.0
Component: Bootstrap
Severity: 5 - Medium
Resolution: Accepted
---------------------------------------------------------------------
Ticket details:
Let's split the discussion about possible bump of our minimum python version (for autotools builds) from #44615.
- Our current python requirement in master is 3.4.
- The oldest environment I still have in active testing (ubuntu trusty) has python-3.4.3
- The second oldest environments in active testing (ubuntu xenial and debian stretch) have python-3.5.2 and python-3.5.3, respectively
- Meson (0.57.0) build has minimum python requirement of 3.6
- Autotools build does not need python when building from a tarball
As for freeciv-3.2, the trusty testing environment is already very limited (the only supported client is sdl2, and even that does not have audio). It wouldn't be a problem to drop "active" testing from that one, and only do occasional builds by first preparing a tarball in a more modern environment. I'd want to keep support for building from the git repo for xenial and stretch.
-> Maybe we should bump minimum python requirement to 3.5 in freeciv-3.2?
As for freeciv-3.3 (-> master as soon as S3_2 has been branched), I'd suggest that we adopt a policy that autotools build python requirement follows meson build minimum requirement (i.e. requirement of the meson itself), as long as build from the tarball does not require python (so that older systems can still use tarballs prepared in newer environment)
--
Ticket information of Freeciv project
Freeciv Project is hosted on OSDN
Project URL: https://osdn.net/projects/freeciv/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/freeciv/ticket/44735
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44735