4 Aug
2020
4 Aug
'20
10:38 a.m.
On 2020-08-04 17:32:00 +0000 (+0000), Jeremy Stanley wrote:
On 2020-08-04 19:09:33 +0200 (+0200), Riccardo Pittau wrote:
After a very interesting and enlightening discussion with Sean and Clark on IRC (thanks!), we were able to test and verify that the issue is related to the latest released version of virtualenv, v2.0.29, that embeds pip 2.20, apparently the real offender here.
[...]
That was indeed confusing. Until I skimmed virtualenv's changelog it hadn't dawned on me that all the problem libraries had a "." in their names.
Er, pip's changelog I meant, of course.
--
Jeremy Stanley