6 Commits

Author	SHA1	Message	Date
Grimmauld	f90a041921	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>	2025-01-09 01:38:27 -08:00
Mark Grassi	844a4dc393	Change string formatting method in Python tests	2023-02-19 16:54:38 -05:00
Mark Grassi	c57138f255	Order imports and module-level dunder name assignments.	2022-08-21 11:15:07 -04:00
David Runge	fda390983f	Fix setuptools version detection in buildpath.py ... libraries/libapparmor/swig/python/test/buildpath.py: The changes introduced in cc7f549665 targetted a wrong setuptools version (61.2). The change in build directory naming has been introduced with 62.1 (1c23f5e1e4).	2022-08-03 10:56:47 +02:00
Ben Greiner	d442584a0a	reviewed edits	2022-07-19 21:47:02 +02:00
Ben Greiner	47d68dac0f	use new build_platlib path with setuptools >= 61.2	2022-07-16 17:47:18 +02:00