Log file Viewer
#pypa logs for Tuesday the 21st of April, 2020
[16:33:46] <sumanah> https://discuss.python.org/t/announcement-pip-20-1b1-beta-release/3960 a beta version of the next release of pip is out! We'd love for you to test it and let us know of bugs
[16:56:47] <sumanah> https://twitter.com/ThePyPA/status/1252641910679879681 is the tweet that you could retweet to help us get more people to test it
[17:52:38] <PSFSlack1> <di> Any way to configure the alpha resolver to be enabled without having to specify `--unstable-feature=resolver` every time?
[17:57:54] <sumanah> di_codes: not right now, but that's an idea we should consider for when it goes from alpha to beta
[17:58:28] <sumanah> I think it's reasonable right now to say "this is so unstable that we want you to have to acknowledge, every time, that this is what you want"
[18:25:24] <PSFSlack1> <di> Hmm, looks like if I set `PIP_UNSTABLE_FEATURE=resolver` as an environment variable, it works
[18:26:24] <PSFSlack1> <di> Actually, I guess I can't really tell. How can I determine which resolver it's using? I don't see anything different when enabling `--verbose`
[19:16:51] <dstufft> assuming it's just using our normal option syntax CLI, env vars, and config file is all handled automatically
[19:18:54] <dstufft> yea, it does not look like it's doing anything special that would bypass that automatic generation
[22:37:23] <techalchemy> anyone know why github would fail to register the fact that i've pushed new releases of something & continue saying an old release is the current one?
[22:46:11] <techalchemy> but for some reason the landing page of my repository indicates that the current release is from 2 tags ago
[23:26:46] <andr_> techalchemy: I believe I've had something similar some time ago only to realize that the newer ones were marked as "pre-releases"