Bug 5657 - raise python requirement
Summary: raise python requirement
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.10.0
Assignee: Pierre Ossman
URL:
Keywords: pcok, relnotes
Depends on:
Blocks: 4120 7196
  Show dependency treegraph
 
Reported: 2015-09-25 10:06 CEST by Pierre Ossman
Modified: 2018-08-15 10:36 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:
* Documentation should list Python 2.6 as the requirement * The installer and tl-setup should verify that Python 2.6 or newer 2.X is used * Autotests should be updated to no longer warn for 2.6 features


Attachments

Description Pierre Ossman cendio 2015-09-25 10:06:43 CEST
It may be time to raise our Python requirement once again. The previous time was three years ago on bug 4213.

The distributions seem to have mostly jumped from 2.4 to 2.6, so let's see what 2.6 means in terms of oldest distribution release:

RHEL 6: 2.6.6
SLE 11: 2.6.8
Debian 6: 2.6.6
Ubuntu 9.04: 2.6.2
Ubuntu 10.10: 2.6.6
Fedora 11: 2.6.0
Fedora 13: 2.6.4
OpenSUSE 11.1: 2.6.0
OpenSUSE 11.3: 2.6.5



Raising the requirements mainly buys us two things:

 - Can start using the system subprocess.py, avoiding conflicts and getting bug fixes (bug 4120).

 - Gives us access to ctypes, which allows us to use pretty much any C API on the system. This gives us a lot more flexibility in what we can do from Python.
Comment 1 Pierre Ossman cendio 2016-02-18 13:35:34 CET
2.5+ also adds the ability to turn off the dangerous implicit relative import in packages:

https://www.python.org/dev/peps/pep-0328/
Comment 8 Pierre Ossman cendio 2018-06-18 12:26:33 CEST
Should be all done now. Documentation updated, tests are passing and product still works fine.
Comment 10 Pierre Ossman cendio 2018-08-14 10:26:12 CEST
Tauthon doesn't look like something that will take off, so I don't think is a concern in practice.

But it doesn't hurt that we are consistent in how we express our requirement, so I don't see any problem updating the error message.
Comment 12 Peter Åstrand cendio 2018-08-15 10:36:15 CEST
Fine now!

Note You need to log in before you can comment on or make changes to this bug.