Jason R. Coombs

> I didn't implement this because I knew it would be difficult to safely handle complex cases lacking a comprehensive [`.mailmap`](https://git-scm.com/docs/gitmailmap)... happy to accept a PR though! I'd be interested...

> At the moment to only way to guarantee dedicated, hyper-responsive, bright-eyed and bushy-tailed support from me personally is via the [one-off](https://github.com/sponsors/casperdcl?frequency=one-time) or [monthly](https://github.com/sponsors/casperdcl?frequency=recurring) sponsor links. I respect that. Thanks...

#108 is a proposal to add the parameter. Please take a look and let me know what you think.

Apologies for not linking to a project that has this issue. To reproduce, you'll want to set up a sphinx docs using `get_outdated_docs` and then build the docs. Here's [one...

I pushed a tag for the commit. `git checkout coverage-1770` should get the commit. It's definitely there, as the github link to the code above is pinned to that commit....

So hard to reproduce the issue reliably :( I see in your run that the `typecheck` job failed, but the others passed. In my run, the `docs` job fails, but...

Here's a more minimal docker image that replicates the missed branch: ```Dockerfile FROM ubuntu:noble ENV TZ=UTC RUN apt update RUN apt install -y software-properties-common RUN apt-add-repository -y ppa:deadsnakes RUN apt...

> > Maybe like they implemented that wrong? cc @BakerNet > > You can use `python -c 'import keyring; keyring.get_credential("", username=None)'` instead > > Looks like a typo in keyring...

It looks like at least one of those uses was fixed in bd1563d421f8799874fc644c5d1ccb5fd8b8071d... so why am I seeing the warning on pip 23.1.2?

The broken usage was introduced in e7449498d39872eb83edd45d22c1983a921c449b. It was fixed again in 1ca4529dc02902830be2a668a4e598f22f154071. It sure would be nice if there were some tests to enforce the desired behavior.