Jason R. Coombs

If it helps, the `keyring` command could emit its `PYTHONPATH` and `sys.executable` for an API caller to call into (not sure I love that idea 😬 ). If only our...

The Python packaging ecosystem is working toward being able to rely on package metadata being present, hence why `importlib_resources` and `importlib_metadata` are unconditionally relying on that metadata being present. To...

With `pep517 0.6`, it's possible to produce metadata for any package including legacy versions this way: ``` draft $ ls draft $ cat > setup.py from distutils.core import setup setup(name='foo',...

Added release notes in 426bf30 and reverted 99 in a96d24f.

This issue is affecting me also. Here's the repro I created: ```python """ Run this file with: pip-run -q -- -m pytest file.py """ __requires__ = ['requests', 'requests_mock', 'pytest'] import...

I can confirm that applying the pending PR does fix the issue: ``` draft $ cat file.py __requires__ = [ 'requests', 'requests_mock@git+https://github.com/jaraco/requests-mock@bugfix-17', 'pytest', ] import requests def test_session(requests_mock): requests_mock.register_uri('GET', '/',...

Hmm. Or maybe only partially fixes the issue. The current patch doesn't work properly if more than one cookie is passed in: ``` draft $ cat two-cookies.py __requires__ = [...

Any thoughts on this change? It's still an issue for me downstream.

I see this PR becomes conflicted with e3bd0d1a92e40fa9cb1d587c59157020a45de620. It's not immediately obvious to me how to reconcile those changes. It's been a long time since I looked into this issue.

Even though this bug is fixed in my branch, the fact that it's not released means that I'm running into [problems releasing jaraco.net](https://github.com/jaraco/jaraco.net/actions/runs/7946487208). I had previously [tried putting the workaround...