Setting up the Python path when developing a library module

Question

I am developing a library and an application that uses the library in Python 2.6. I placed the file "mylib.pth" in "site-packages" so that I can import mylibfrom my application.

I use DVCS, so when I want to fix a bug or add a function to the library, I make a repository branch and work in that branch. To test my application with changes made to the library, I edit the path in "mylib.pth" to point to a new development branch.

This is a bit tedious if I have several parallel branches of my library running on one. I have to continue editing the "mylib.pth" file before testing to make sure that I am testing the correct version of my library. Is there a way to use the current path (i.e. the development branch of the library I'm in) to set the library path when calling my application instead of using "mylib.pth" in the global "package sites" directory?

Answer 1

Is virtualenv what you are looking for? From the description:

, , 1 LibFoo, 2. ? /usr/lib/python 2.4/site-packages ( ), , , .

Answer 2

: Python Hacker: Virtualenv, Fabric Pip. Python.

Answer 3

setuptools, setup.py develop , .pth.

Answer 4

, sys.path, ( ) . site.addsitedir - . Python, , , ; os.path.normpath , , - .

sitecustomize.py , .

Answer 5

zc.buildout. python.

Answer 6

I installed my own PYTHONPATHto indicate the latest version. No editing.

export PYTHONPATH=.:/the/new/version