Up to [cvs.NetBSD.org] / pkgsrc / lang / py-python-discovery
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-python-discovery: updated to 1.6.7 1.6.7 (2026-10-28) Fixed - Rank uv's minor version links behind the concrete install on Windows too, where uv creates them as directory junctions that ``Path.is_symlink()`` does not report - Stop a venv lookup from rewriting the ``executable`` of earlier results, ``PythonInfo.current()`` and ``PythonInfo.current_system()`` when they share its base interpreter
py-python-discovery: updated to 1.6.6 1.6.6 Bug fixes Treat version specifiers with an item that cannot be parsed, such as >=3.x, >=3.12 <4 or >=3.12,foo, as literal executable paths instead of raising a bare AssertionError or ignoring the item during discovery Accept relative interpreter paths that step up a directory, such as ../venv/bin/python, which were found and queried but never matched the spec Match ~=X.Y compatible-release specifiers against later minor versions, as PEP 440 defines, instead of only the same minor; ~=3.10 now accepts 3.11 and newer 3.x
py-python-discovery: updated to 1.6.4 v1.6.4 (2026-10-19) Improved documentation - 1.6.4 - Clarify the executable paths accepted by ``try_first_with`` in the standalone usage example. (:issue:`150`) v1.6.3 (2026-10-16) Bug fixes - 1.6.3 - Treat specs with dot-only version components, such as ``python.``, as literal executable paths instead of raising ``IndexError`` - Pass PEP 514 ``ExecutableArguments`` to registered Windows interpreters when querying them, so a registration that points at a launcher such as ``py.exe -3.11`` reports the interpreter it selects (:issue:`148`) v1.6.2 (2026-10-10) Bug fixes - 1.6.2 - Discard malformed interpreter cache entries and query the interpreter again, including entries with missing, non-string or unusable ``system_executable`` paths - Use the default interpreter query timeout and warn for invalid ``PY_DISCOVERY_TIMEOUT`` values. Accept ``inf`` or values above the subprocess wait limit to disable the timeout
py-python-discovery: updated to 1.6.1 1.6.1 docs(py_info): cover system_exe in all four dimensions fix(discovery): skip empty PATH entries
py-python-discovery: updated to 1.6.0 Features - 1.6.0 - :attr:`~python_discovery.PythonInfo.system_exe` returns the executable of the system Python an interpreter is based on, falling back to :attr:`~python_discovery.PythonInfo.executable` the way :meth:`~python_discovery.PythonInfo.resolve_to_system` does. :attr:`~python_discovery.PythonInfo.system_executable` is ``None`` until resolution runs, so every consumer had to narrow a value discovery has already settled - by :user:`gaborbernat`. (:issue:`127`)
py-python-discovery: updated to 1.4.4 Bug fixes - 1.4.4 - Parse the debug build flag in interpreter specs - ``python3.13d`` and Debian's ``python3.13-dbg`` / ``python3.13-debug`` now select a ``Py_DEBUG`` interpreter instead of being misread as an ISA named ``dbg``. Resolving a virtualenv to its base interpreter also checks the free-threaded and debug ABI flags, so a debug or free-threaded environment no longer resolves to a release build of the same version
py-python-discovery: updated to 1.4.2 Bug fixes - 1.4.2 - Stop executable symlink resolution once the stdlib landmark is reachable and keep macOS framework builds untouched, matching ``getpath`` - Homebrew interpreters no longer get version-pinned ``Cellar`` paths recorded and stable aliases such as Debian's ``/usr/bin/python3`` are preserved Bug fixes - 1.4.1 - Resolve executable-only symlinks when computing ``system_executable``, mirroring CPython's ``getpath.realpath`` (python/cpython115237): a symlink to the interpreter binary now resolves to the real interpreter, while a fully symlinked interpreter tree is kept as-is
py-python-discovery: updated to 1.4.0 1.4.0 - Add ``debug_build`` attribute to :class:`PythonInfo` exposing whether the interpreter is a debug build (``Py_DEBUG``)
py-python-discovery: updated to 1.3.1 Bug fixes - 1.3.1 - export normalize_isa and deprecate KNOWN_ARCHITECTURES - discover uv-managed Pythons on Windows. Previously the glob assumed Unix layout (``<root>/<key>/bin/python``) and silently found nothing on Windows, where uv places ``python.exe`` directly under the install root - Canonicalize GraalVM to match GraalPy Python interpreter in PythonSpec and PythonInfo.
py-python-discovery: updated to 1.3.0 1.3.0 feat(discovery): add iter_interpreters for enumeration
py-python-discovery: updated to 1.2.2 1.2.2 export normalize_isa and deprecate KNOWN_ARCHITECTURES
py-python-discovery: updated to 1.1.3 1.1.3 fix(test): add loongarch64 to known ISAs
py-python-discovery: updated to 1.1.2 1.1.2 docs: add package description and usage to README fix(subprocess): drain pipes after killing timed-out process fix(discovery): match prerelease versions against major.minor specs
py-python-discovery: added version 1.1.0 You may have multiple Python versions installed on your machine -- system Python, versions from pyenv, mise, asdf, uv, or the Windows registry (PEP 514). python-discovery finds the right one for you. Give it a requirement like python3.12 or >=3.11,<3.13, and it searches all known locations, verifies each candidate, and returns detailed metadata about the match. Results are cached to disk so repeated lookups are fast.