2016-07-17 23:35:39 +02:00
|
|
|
sudo: travis
|
2012-06-22 09:53:31 +02:00
|
|
|
language: python
|
2016-01-20 21:18:22 +01:00
|
|
|
python: 3.5
|
2014-01-07 16:49:44 +01:00
|
|
|
env:
|
|
|
|
|
- TOX_ENV=py27
|
|
|
|
|
- TOX_ENV=py33
|
2015-02-16 00:09:13 +01:00
|
|
|
- TOX_ENV=py34
|
2016-01-20 21:18:22 +01:00
|
|
|
- TOX_ENV=py35
|
2014-01-07 16:49:44 +01:00
|
|
|
- TOX_ENV=pypy
|
2012-06-22 09:53:31 +02:00
|
|
|
|
Update Tests for New Twine
* Updated .travis.yml to fix PEP 440 warnings
* Fixed twine calls
We were getting test failures on multiple branches in
`test_server.py`. I first investigated a warning message
popping up in every test run:
```
PEP440Warning,
/home/travis/virtualenv/python3.5.2/lib/python3.5/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (git-0.4.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
```
Moving the installation of setuptools, pip, sphinx, and tox
into the `install` key for Travis resolved that issue, but
`test_server.py` tests were still failing. It turns out that
Twine 1.7.0 added support for SSL cert specification and,
in the process, changed the call signature for the `upload`
and `register` internal methods.
This PR fixes the calls so that they align with Twine's new
function signature. Note that tests now fail on Twine <1.7.0,
so I have also updated the dev requirements file.
2016-07-17 20:40:06 +02:00
|
|
|
install:
|
|
|
|
|
- pip install -U setuptools pip sphinx tox
|
|
|
|
|
|
2014-01-07 16:49:44 +01:00
|
|
|
script:
|
2015-09-14 00:35:38 +02:00
|
|
|
- ./bin/test_standalone.sh
|
2015-09-16 23:54:41 +02:00
|
|
|
- tox -e $TOX_ENV
|
2016-06-28 11:18:39 +02:00
|
|
|
- ./bin/check_readme.sh
|
2012-12-02 23:22:54 +01:00
|
|
|
|
|
|
|
|
branches:
|
|
|
|
|
except:
|
|
|
|
|
- standalone
|