python-guide/docs/shipping/packaging.rst

Packaging Your Code
===================

Packaging your code is important.


For Python Developers
:::::::::::::::::::::

If you're writing an open source Python module, `PyPI <http://pypi.python.org>`_, more properly known as *The Cheeseshop*, is the place to host it.



Pip vs. easy_install
--------------------

Use pip.  More details `here <http://stackoverflow.com/questions/3220404/why-use-pip-over-easy-install>`_


Personal PyPI
-------------

If you want to install packages from a source different from PyPI, (say, if
your packages are *proprietary*), you can do it by hosting a simple http server,
running from the directory which holds those packages which need to be installed.

**Showing an example is always beneficial**

Say if you are after installing a package called MyPackage.tar.gz,  and assuming this is your directory structure


- archive
   - MyPackage
       - MyPackage.tar.gz

Go to your command prompt and type:
::

$ cd archive
$ python -m SimpleHTTPServer 9000

This runs a simple http server running on port 9000 and will list all packages (like **MyPackage**). Now you can install **MyPackage** using any python package installer. Using Pip, you would do it like:
::

$ pip install --extra-index-url=http://127.0.0.1:9000/ MyPackage

Having a folder with the same name as the package name is **crucial** here.
I got fooled by that, one time. But if you feel that creating a folder called
**MyPackage** and keeping **MyPackage.tar.gz** inside that, is *redundant*, you can still install MyPackage using:
::

$ pip install  http://127.0.0.1:9000/MyPackage.tar.gz

Chishop
+++++++


For Linux Distributions
::::::::::::::::::::::::

Useful Tools
------------

- epm
- alien