Poetry is incompatible with unstable-tagged Python builds (Invalid PEP 440 version: '3.Y.Z+')

I’v just installed Python3.11 from deadsnakes/nightly.

Poetry can’t use it, because the Python version has a + in it.

Invalid PEP 440 version: '3.11.0+' is all I get 😭

P.S. if the wise men declare that deadsnakes is at fault here, I’ll happily bug dead snakes.

[neersighted]

My thinking is we should centralize it using a parse_python_version() variant that encapsulates the stripping of the + so we don’t randomly proliferate it in the codebase and get burned by a future omission. The parse_python_version() code can just be a preprocessing before we hand it to our regular version parsing code, and can be unit tested; we should also end-to-end test the main usage (in env.py).

[eamanu]

Hi, what about something like this? (it works in my local tests in Debian)

Index: src/poetry/utils/env.py
===================================================================
--- src/poetry/utils/env.py	2022-11-30 20:30:11.425524136 -0300
+++ src/poetry/utils/env.py	2022-11-30 20:30:31.829803450 -0300
@@ -1618,7 +1618,7 @@
             "platform_release": platform.release(),
             "platform_system": platform.system(),
             "platform_version": platform.version(),
-            "python_full_version": platform.python_version(),
+            "python_full_version": platform.python_version().rstrip("+"),
             "platform_python_implementation": platform.python_implementation(),
             "python_version": ".".join(platform.python_version().split(".")[:2]),
             "sys_platform": sys.platform,