Re: git: 58e57b3edeef - main - deskutils/py-khard: Update 0.19.1 => 0.20.0, undeprecate, take maintainership
- Reply: Vladimir Druzenko : "Re: git: 58e57b3edeef - main - deskutils/py-khard: Update 0.19.1 => 0.20.0, undeprecate, take maintainership"
- In reply to: Vladimir Druzenko : "Re: git: 58e57b3edeef - main - deskutils/py-khard: Update 0.19.1 => 0.20.0, undeprecate, take maintainership"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 29 Jul 2025 10:24:13 UTC
Am 29.07.2025 um 13:18 schrieb Vladimir Druzenko: > Do I understand correctly that "USES=python:-3.11" also implies 2.7? > I didn't expect this… just check Mk/Uses/python.mk: # Feature: python # Usage: USES=python[:version-spec][,arg,...] # Valid ARGS: <version-spec>, patch, build, run, test, env # # version-spec Declarative specification for the Python version(s) the # port supports. Subsets and ranges can be specified: # # * <version> # * <minimum-version>-<maximum-version> # * <minimum-version>+ # * -<maximum-version> # # Examples: # # USES=python:2.7 # Supports Python 2.7 Only # USES=python:3.9+ # Supports Python 3.9 or later # USES=python:3.9-3.10 # Supports Python 3.9 to 3.10 # USES=python:-3.9 # Supports Python up to 3.9 # USES=python # Supports 3.9+ # # NOTE: <version-spec> should be as specific as possible, matching the versions # upstream declares support for, without being incorrect. In particular, # USES=python *without* a <version-spec> means 3.9+, # including unreleased versions, which is probably incorrect. # # Not specifying a <version-spec> should only be used when a more specific # <version-spec> cannot be specified due to syntax limitations, for # example: 2.7,3.9-3.10, but even in this case, X.Y+ (2.7+), or -X.Y (-3.9) # is preferred and likely more correct. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook