Re: [gpsd-dev] Minimum Python Version

[Greg Troxel]

Fred Wright <address@hidden> writes:

> The best fix for this (where practical) is to make the code
> Python3-compatible and go back to the generic "python" in the shebang
> lines.  Since many Python3 features have been backported to 2.6, it's a
> lot easier to write "Python2/3" code if one can assume that Python2 is at
> least Python2.6.

The right fix is for gpsd's build process to find a suitable python
implemention via searching for fully-qualified names, and then to
substitute that path into the files at build (or perhaps install, while
also workign for make check) time.

One of the issues in the general case is that one has to check for
python libraries, which are installed separately per version.  So having
the version change after configure/build is unsound.  gpsd may avoid
this currently, but avoiding the issue is an unusual special case.

> The Python version specification in build.txt is "Python 2.x, x >= 6", but
> strictly speaking, that's a *build* requirement, not a *run* requirement.
> I wasn't able to find any user-level "system requirements" documentation
> giving a minimum Python version for end users to run the Python programs.

I think it's understood that one has to run with the same version that
was found at build time.

signature.asc
Description: PGP signature