Closed cz-siq closed 1 year ago
I can tell you that I published this today, and from my computer, the "Got" hash is the same as mine.
$ sha256sum dist/wcwidth-0.2.6-py2.py3-none-any.whl
795b138f6875577cd91bba52baf9e445cd5118fd32723b460e30a0af30ea230e dist/wcwidth-0.2.6-py2.py3-none-any.whl
I'll continue looking into what this might mean.
The sdist for 0.2.6 was uploaded on 15th January with a SHA256 of a5220780a404dbe3353789870978e472cfe477761f06ee55077256e509b156d0.
The wheel for 0.2.6 was uploaded today with a SHA256 of 795b138f6875577cd91bba52baf9e445cd5118fd32723b460e30a0af30ea230e.
Please update your requirements/develop.txt
to match.
Click "view hashes" at https://pypi.org/project/wcwidth/#files to confirm.
Thank you, @hugovk !
How do we fix this? Installs are failing.
@dashmug Replace:
a5220780a404dbe3353789870978e472cfe477761f06ee55077256e509b156d0
With:
795b138f6875577cd91bba52baf9e445cd5118fd32723b460e30a0af30ea230e
@jquast the problem seems to be the delay in upload of the wheel. Any chance you could publish .tar.gz and wheel .zip at the same time in the future? E.g. python3.11 setup.py sdist bdist_wheel
would produce both files and then twine can upload both at the same time. That should solve the problem for everyone, since Dependabot picks up all hashes the first time then. Thank you! :pray:
Sorry for the problem, I will try better next release
@jquast thank you!
Hi,
Got below hash error today. Do you have an idea what could have caused it?
Thanks!