Skip to content

Instantly share code, notes, and snippets.

@reginafcompton

reginafcompton/cutting-a-new-pypi-release.md

Last active March 19, 2018 14:42
Show Gist options
  • Save reginafcompton/9874ab534951412265a0a8af48972784 to your computer and use it in GitHub Desktop.
Save reginafcompton/9874ab534951412265a0a8af48972784 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
cutting-a-new-pypi-release.md

Cutting a new pypi release: The case of django-councilmatic

Have you and your friends been making lots of changes to django-councilmatic? are you ready to cut a new release in pypi? Take these steps.

  • Summarize your changes in RELEASENOTES.md.

  • On a branch, visit setup.py and adjust the version of django-councilmatic, e.g. version='0.6.9' becomes version='0.6.10'

  • Push changes to GitHub and merge.

  • Locally, return to master, and pull changes down.

  • Run python setup.py sdist- it will create a new distribution in a dist directory.

  • You should be in a virtualenv that has twine installed. In not, then install it: pip install twine.

  • Then, upload this release to pypi:

twine upload dist/<name dist file>

You can see your new version on pypi.python.org!

N.B. For all this to work, you need a .pypirc file in your home directory (/Users/<username>). Add the following:

[distutils]
index-servers =
  pypi

[pypi]
username:<username>
password:<your password>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment