Pypi deployment using Travis CI

[s-celles]

Deployment to Pypi of new release using Travis CI should be done using:
https://docs.travis-ci.com/user/deployment/pypi/

[s-celles]

Same as https://github.com/python-constraint/python-constraint/blob/master/RELEASE_PROCEDURE.md

[ocefpaf]

@scls19fr you can accomplish that by adding the following lines at the end of your .travis.yaml file:

deploy:
  skip_cleanup: true
  provider: pypi
  user: PYPI_USERNAME
  password:
    secure: TRAVIS_ENCRYPTED_PYPI_PASSWORD
  distributions: sdist bdist_wheel
  upload_docs: no
  on:
    repo: python-windrose/windrose
    tags: true
    all_branches: master
    condition: '$TEST_TARGET == "default"'

You will need to add the PYPI_USERNAME and the TRAVIS_ENCRYPTED_PYPI_PASSWORD.
The latter can be generated with Travis-CI CLI and the command:

travis encrypt -r python-windrose/windrose

[s-celles]

I used much less parameters in https://github.com/python-constraint/python-constraint/blob/master/.travis.yml and latest release seems to have been published correctly https://pypi.org/project/python-constraint/

I had modified my .travis.yml https://github.com/python-windrose/windrose/blob/master/.travis.yml#L33-L39 the same way.

but your setting probably have some benefits

[ocefpaf]

but your setting probably have some benefit

The only benefits is IMO is the

distributions: sdist bdist_wheel

that will will publish both wheels and source distribution.

The 3 extras options in the on field will ensure that the upload will occur only when those conditions are met. However, you probably don't need the last one, unless you have multiple tests conditions, and if you plan to issue releases from other branches/repos you may want to avoid the other conditions.