In my experience (as a tester), it is easier to deal with PYTHONPATH than to add the my.pth file to the site-packages directory. The main reason is that I have my custom packages and modules in a directory tree that I deploy on many clients/servers/platforms/OS versions, some running different versions of Python. I found that I solve my import problems by adding one line to .bash_profile, which sets PYTHONPATH to the parent directory of my custom directory tree. Or, on Windows, I add an Environment variable, call it PYTHONPATH, and set it to the necessary directory. The alternative would be to hunt for the site-packages directory (of which there might be several) on all my systems.
I guess it's a matter of taste in the end, but I do find the PYTHONPATH approach more suitable for automation and scripting, particularly when dealing with a large number of systems. Grig -- http://mail.python.org/mailman/listinfo/python-list
