On 1/2/23, Brennan Ashton <bash...@brennanashton.com> wrote:
> On Mon, Jan 2, 2023, 4:46 AM Alan C. Assis <acas...@gmail.com> wrote:
>
>> Thank you very much Brennan,
>>
>> I was afraid to change the hash because I wasn't sure that the file
>> wasn't corrupted/infected.
>>
>> How did you check it was a legit hash change?
>>
>
> In the PR I linked to the relevant upstream issue. It was not an incorrect
> hash (note both still exist in the Pipenv.lock) it is that for the same
> version a whl was uploaded to pypi (which we prefer) and that was not
> listed.
>

Right, understood! Thank you!

Reply via email to