Currently if the repository is consistent_snapshot, Updater will prefix the target filename with the hash when constructing the download URL. In the Warehouse case this is not wanted (warehouse target file paths are "consistent", even if the filenames are not).
This is an example of a working URL:
https://files.pythonhosted.org/packages/ca/ab/5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f/Django-3.0.8-py3-none-any.whl
But currently Updater will try to download
https://files.pythonhosted.org/packages/ca/ab/5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f/caab5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f.Django-3.0.8-py3-none-any.whl
If there is no way to figure this out automatically, then there should probably be a way to tell Updater that I Know What I'm Doing, don't prefix filenames.
Currently if the repository is
consistent_snapshot, Updater will prefix the target filename with the hash when constructing the download URL. In the Warehouse case this is not wanted (warehouse target file paths are "consistent", even if the filenames are not).This is an example of a working URL:
https://files.pythonhosted.org/packages/ca/ab/5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f/Django-3.0.8-py3-none-any.whl
But currently Updater will try to download
https://files.pythonhosted.org/packages/ca/ab/5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f/caab5e004afa025a6fb640c6e983d4983e6507421ff01be224da79ab7de7a21f.Django-3.0.8-py3-none-any.whl
If there is no way to figure this out automatically, then there should probably be a way to tell Updater that I Know What I'm Doing, don't prefix filenames.