Zanie Blue
Zanie Blue
Before putting a lot of effort into snapshot correctness, you should probably see if this actually helps performance on the tests that _do_ pass.
I was hoping for much more than that, though it's still nice. I wonder where we're spending all of our time in that case?
FWIW I tried to setup squid today and it's non-trivial because you still need to have it support SSL, which requires a self-signed cert etc. Annoyingly the image at `ubuntu/squid`...
And for posterity, I tried using Caddy and Nginx but both are not really designed for caching a forward proxy.
I used this one-liner for a self-signed cert ``` openssl req -x509 -out localhost.crt -keyout localhost.key \ -newkey rsa:2048 -nodes -sha256 \ -subj '/CN=localhost' -extensions EXT -config
Does that switch to using HTTP instead of HTTPS? I sort of don't think so, it just ignores bad certificates.
This continues to look quite challenging, though I think it would be very valuable I don't think there's a clear path forward for this pull request.
Thanks for the thorough report. Does this occur on the latest version? There's been a lot of resolver work in the last few weeks.
Hi! I think you just need to disambiguate that it's a file path and not a package name, e.g. with `./python_dotenv-1.0.1-py3-none-any.whl`. @charliermarsh I wonder if we should detect this automatically...
I think we should also add a hint to resolver errors when the package is not found in the registry but the name exists in the working directory.