apparmor/libraries/libapparmor/swig/python/test/buildpath.py

#!/usr/bin/python3
# the build path has changed in setuptools 62.1:
# https://github.com/pypa/setuptools/commit/1c23f5e1e4b18b50081cbabb2dea22bf345f5894
import sys
import sysconfig

import setuptools


if tuple(map(int, setuptools.__version__.split(".")[:2])) >= (62, 1):
    identifier = sys.implementation.cache_tag
else:
    identifier = "%d.%d" % sys.version_info[:2]
print("lib.{}-{}".format(sysconfig.get_platform(), identifier))
reviewed edits 2022-07-19 21:47:02 +02:00			`#!/usr/bin/python3`
Fix setuptools version detection in buildpath.py libraries/libapparmor/swig/python/test/buildpath.py: The changes introduced in https://gitlab.com/apparmor/apparmor/-/commit/cc7f549665282c0a527d5424a6f9d726c50ddbb1 targetted a wrong setuptools version (61.2). The change in build directory naming has been introduced with 62.1 (https://github.com/pypa/setuptools/commit/1c23f5e1e4b18b50081cbabb2dea22bf345f5894). 2022-08-02 14:17:27 +02:00			`# the build path has changed in setuptools 62.1:`
			`# https://github.com/pypa/setuptools/commit/1c23f5e1e4b18b50081cbabb2dea22bf345f5894`
use new build_platlib path with setuptools >= 61.2 2022-07-16 00:42:14 +02:00			`import sys`
			`import sysconfig`
Order imports and module-level dunder name assignments. 2022-08-07 20:32:07 -04:00
use new build_platlib path with setuptools >= 61.2 2022-07-16 00:42:14 +02:00			`import setuptools`
Fix setuptools version detection in buildpath.py libraries/libapparmor/swig/python/test/buildpath.py: The changes introduced in https://gitlab.com/apparmor/apparmor/-/commit/cc7f549665282c0a527d5424a6f9d726c50ddbb1 targetted a wrong setuptools version (61.2). The change in build directory naming has been introduced with 62.1 (https://github.com/pypa/setuptools/commit/1c23f5e1e4b18b50081cbabb2dea22bf345f5894). 2022-08-02 14:17:27 +02:00

limit buildpath.py setuptools version check to the relevant bits previously, this check would fail if the setuptools version would contain non-integers. On my system, that is the case: `setuptools.__version__` is `'75.1.0.post0'` I believe it is entirely fair to just check the relevant bits and refuse to continue if those can not be checked properly. But haviong something extra on the version should not immediately cause issues (e.g. the `post0` here, or slugs like `beta`, `alpha` and the likes). Probably only very few systems are running setuptools with weird version info, but supporting this doesn't cost much, i believe. (cherry picked from commit 3302ae98e42b0a02018d4c743aa71c179377c274) Signed-off-by: John Johansen <john.johansen@canonical.com> 2024-12-11 12:23:27 +01:00			`if tuple(map(int, setuptools.__version__.split(".")[:2])) >= (62, 1):`
use new build_platlib path with setuptools >= 61.2 2022-07-16 00:42:14 +02:00			`identifier = sys.implementation.cache_tag`
			`else:`
			`identifier = "%d.%d" % sys.version_info[:2]`
Change string formatting method in Python tests 2023-02-19 16:26:14 -05:00			`print("lib.{}-{}".format(sysconfig.get_platform(), identifier))`