pip 8.1.1 from /usr/lib/python2.7/dist-packages (python 2.7)
I can see my package live at https://pypi.python.org/pypi/fontbakery/0.3.3
But I get this when doing pip install:
https://github.com/pypa/twine/issues/281
I did this:
# cleanup
rm build/ -rf
rm dist/ -rf
rm venv/ -rf
# create a fresh python virtual env
virtualenv venv
. venv/bin/activate
# Remove the '-git' suffix and bump up the version number on setup.py
vim setup.py
git add setup.py
git commit -m "Updating version in preparation for a new release"
# install fontbakery on it and run our code tests
pip install .
pip install pytest
pytest Lib/fontbakery --verbose
# crate the package
python setup.py bdist_wheel
# Register a git tag for this release and publish it
git tag -a v0.3.3 -m "FontBakery version 0.3.3 (2017-11-23)"
git push upstream --tags
# and finally upload the new package to PyPI
twine upload dist/*
# Then we append a '-git' suffix on setup.py
vim setup.py
git add setup.py
git commit -m "Adding '-git' to version for the next release cycle"
It's weird, https://pypi.python.org/simple/fontbakery does not list the 0.3.3 version. Using warehouse instead works: pip install -i https://pypi.org/simple
.
There's also a 0.3.3-rc1 version I pushed to PyPI yesterday that is still not showing up on pip's list of available versions, while being good at PyPI as well:
0.3.3 and 0.3.3rc1 were uploaded yesterday. All other versions (the ones that show up on pip's list) were uploaded in the past (like more than a month ago). If I recall correctly the procedure for uploading 0.3.2 was roughly the same (if not actually identical) to what I did yesterday, since I followed the same documentation - notes written by myself on the past and published on fontbakery's README.md:
https://github.com/googlefonts/fontbakery/blob/6b998b0741a1f75311b8edeb59175ac8bf80d383/README.md#font-bakery-maintenance
Hi @felipesanches!
So, it seems PyPI-legacy is not purging the Fastly cache correctly. If you run curl -X PURGE https://pypi.python.org/simple/<package-name>
, that should fix the problem. I recently saw this at https://github.com/pypa/warehouse/issues/2608.
I suggest you also make an issue over at github.com/pypa/pypi-legacy about this and link it here. :)
I suggest you also make an issue over at github.com/pypa/pypi-legacy about this and link it here. :)
Ignore this. @di made one. :)
This can be closed, the issue was identified & fixed over at https://github.com/pypa/pypi-legacy/issues/739.
thanks!
@davelab6 FYI
@pradyunsg Your solution using PURGE
worked, except that I had to use https://pypi.org/simple/<package-name>/
instead.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
Hi @felipesanches!
So, it seems PyPI-legacy is not purging the Fastly cache correctly. If you run
curl -X PURGE https://pypi.python.org/simple/<package-name>
, that should fix the problem. I recently saw this at https://github.com/pypa/warehouse/issues/2608.I suggest you also make an issue over at github.com/pypa/pypi-legacy about this and link it here. :)