Fran García Salomón

> Did you try building and it failed? The build doesn't fail and tesserocr works as expected. I'd say that this issue can be closed.

Yes, `keyring` is on my `$PATH`.

It didn't work, I got the same error. FYI, I'm using a virtual env and `keyring` is installed in it (my `$PATH` includes the virtual env). Could be this a...

I think the problem is that when calling `keyring` as a subprocess it requires that a `username`[ is passed through the URL](https://pip.pypa.io/en/stable/topics/authentication/#using-keyring-as-a-command-line-application). Looking at pip's code it seems that if...

> Hmm, could you try `_json_key_base64` (that literal string) as the `username`? [cloud.google.com/artifact-registry/docs/python/authentication](https://cloud.google.com/artifact-registry/docs/python/authentication) seems to suggest that Google's Artifact Registry will accept that. > > And if that doesn't work,...

> Dang. Just to confirm: _json_key_base64 didn't work in either the URL or the .pypirc, right? It didn't work (I'm not using a service account key BTW) ---- To me...

I found this [issue](https://github.com/pypa/pip/issues/11971) that address the username problems. But it didn't work for me 🤔. And also there is this other [issue](https://github.com/pypa/pip/issues/11827). So, as you said, #743 is the...

FYI: I'd the chance to test this again and using `oauth2accesstoken` as the username in the Google Artifact Registry worked as pointed [here](https://github.com/pypa/pip/issues/11971). I think this issue can be closed...

> It's impossible to use this library. It looks that something is wrong with the published artifact on maven, but you can build the library on your own with `./gradlew...