Skip to content

Uploading To PIP

Jump to bottom
James Draper edited this page Dec 8, 2016 · 5 revisions

MAINTAINERS ONLY

Make sure you have the appropriate permissions on your pip account. If you don't file an issue and @draperjames or @zbarge will get back to you.

Update the version number

Make sure the version number has been altered accordingly.

major.minor.patch
  • Major version numbers change whenever there is some significant change being introduced. For example, a large or potentially backward-incompatible change to a software package.
  • Minor version numbers change when a new, minor feature is introduced or when a set of smaller features is rolled out.
  • Patch numbers change when a new build of the software is released to customers. This is normally for small bug-fixes or the like.

Derived from this stackoverflow question

Upload to pip

Using twine

  1. Open the command prompt and cd to your build directory.
  2. Create your distribution.
python setup.py sdist bdist_wheel
  1. Upload packages
twine upload dist/*

You'll be prompted for you credentials. Enter them and then your done!
You should delete the files created by twine if you expect to run twine again. It gets all pissy when you have a couple different version of the same package in the dist directory. All of the files have been marked in the .gitignore file so you won't have to worry about pushing them.

With travis.ci

We can also automate the deployment to PIP with travis. I(@draperjames) will try to implement this later on.

Clone this wiki locally