Mark Adamson

~can you give a tip on how we set this to restore original behaviour? It doesn't seem to be a property on `APIGatewayProxyFunction` and it's not clear which functions inherit...

> can you give a tip on how we set this to restore original behaviour? It doesn't seem to be a property on `APIGatewayProxyFunction` and it's not clear which functions...

I'm pretty confused by how to get keyring to work, without needing users to either change their path or manually install keyring and my keyring extension in every single repository...

> If the global python is on the path, or more specifically the path where `pip install keyring` puts the `keyring` executable, then you could tell people to `pip install...

Still not really working after manually installing keyring and our extension. This works fine and shows it pulling requests from my authenticated store (AWS code artifact): `python -m pipenv run...

Looks like I got it working (with a warning). `set PIP_KEYRING_PROVIDER=import` > Locking [packages] dependencies... > Building requirements... > Resolving dependencies... > Success! > [====] Locking...Warning: WARNING:pipenv.patched.pip._internal.network.auth:Keyring is skipped due...

I'll check further, it didn't manage to lock before I told it to use keyring, it did succeed afterwards, but with those warnings. pipx sounds helpful thanks. We do use...

I've got a bit further after debugging into pipenv. It seems that there are two types of call made to keyring, one succeeds the other fails, in pipenv.patched.pip._internal.network.auth ```python try:...

The lack of username is easier to workaround than the lack of URL path, as we return different credentials for some url paths.

ok, I know what it is. ~It probably isn't a bug, though there might be something better that would help this rather niche case.~ It is a bug I believe,...