pypi and setuptools #105
pypi and setuptools #105
Conversation
….7 python. Switch from disutils to setuptools in setup.py
| repo: jrxFive/python-nomad | ||
| condition: $TRAVIS_PYTHON_VERSION = "2.7" | ||
|
|
||
| condition: $TRAVIS_PYTHON_VERSION = "3.7" |
There was a problem hiding this comment.
Hmm yeah, the one working example I have of a deploy stage in Travis uses python 3.7 so maybe that's it 🤷♂️
|
Probably need to retrigger those builds to get the correct status reflected here (if you care to). travis.org was having a bit of an outage yesterday along those lines... (edit: I went ahead and restarted em) |
|
Oh! And for what it's worth, when I needed to validate travis + pypi publishing logic in the past, I have used a corresponding entry on https://test.pypi.org/ / https://packaging.python.org/guides/using-testpypi/. In my situation, I added a commit in another branch with a commit to point Travis at the test server url, pushed that up to a fork, and then did a tagged release on the fork to trigger the deploy condition. Ref: https://docs.travis-ci.com/user/deployment/pypi/#releasing-to-a-self-hosted-pypi |
|
Yea def need to check out the test pypi! If this doesn't work on merge will do that with a follow up branch... |
Unsure if travis is using twine for pypi upload, possibly why it failed on python 2.7?