Home Company Services Portfolio Contact us nav spacer

From own SVN to collective SVN to Pypi

by hedley — posted on Apr 14, 2009 05:09 PM — last modified Apr 14, 2009 05:09 PM

This describes the procedure to move a product from your own SVN repo to the collective SVN repo. Finally it shows how to publish the egg to pypi.python.org.

An SVN import is required since it preserves the SVN commit history.

cd /tmp
svn co https://svn.mydomain.com/svn/my.product
svn import my.product https://svn.plone.org/svn/collective/my.product \
--username myname -m "Initial import"
Make a checkout from collective. Your own SVN repo must now cease to exist.

  1. Make sure your product is packaged in a setuptools-compatible way (i.e. it is installable via 'python setup.py install').
  2. Check the metadata in your package's setup.py file to make sure you've got the basic required information included so people will know what your package does.
  3. Ensure that the setup.cfg file has tag_svn_revision = False, else the egg will have an ugly title.

We are now ready to release to pypi. You must have a user account on pypi to be able to make releases.

  1. Run 'python setup.py register' to register your product with the pypi database.
  2. Run 'python setup.py sdist bdist_egg upload' to simultaneously create a source distribution and egg and upload it to pypi.
Document Actions