Paul "TBBle" Hampson

A quick poke at the history of the relevant file suggests #7978 was the fix, appearing in Poetry 1.5.1 and later. Note for self: Before cleaning up https://github.com/TBBle/poetry/tree/allow-exact-pre_release-child-dependencies, check that...

You'd have to implement the same registry searching logic documented in PEP-514. I had a quick look last month, and my recollection is that this is basically all pep514tools is...

Flicking through this, I noticed a couple of unremoved TODOs that I think are being resolved by the adjacent changes, and also (not in this PR, but while checking context)...

Probably a duplicate of #1200. Certainly the same error, with a possibly-different cause.

It'd be interesting to know if the MS Store Python install is PEP 514-compliant. `py` as of Python 3.11 is a PEP 514 implementation, so anything PEP 514-compliant should show...

Which version of `py` are you using? My understanding of PEP 514 was that the registry keys used by `py` were effectively grandfathered in, so a PEP 514-consuming tool (including...

I just had a quick look, and given I'm in a venv on a machine with only older Python installed, and no Python in my `PATH`... ```console > py --list...

The prior PR for this approach that I could find is #4217. The comments seem to cover the main concerns with this approach, and was closed in favour of a...

Yeah, that would make sense too, since [`py.exe` has been rewritten in Python 3.11 as a PEP-514-consuming tool](https://github.com/python/cpython/issues/90724), so the results should be consistent.

I'm closing this ticket in favour of #2117, since with Python 3.11's `py` consuming the PEP-514 data, I think it'd be better to consume that directly than try and wrap...