It’s been crazy over the last couple of months with the book and with starting a new job, so I’ve been slack on blogging. Well, I’m trying to get back in the saddle again, so I’ll briefly mention something here that I only discovered recently.
If you are working on code that you are planning to release as an egg, it can be a huge pain to go through the code->bdist_egg->easyinstall->test cycle, slightly less of a pain to do code->setup.py install->test, and slightly less of a pain still to do export PYTHONPATH=/path/to/my/project->code->test. But there is a better way. If you do “easy_install develop”, then you can just enter into a code->test cycle. This option puts a .pth file in your site-packages directory and points to the set of code you’re working on. This keeps you from having to redeploy your code every time you want to test something. It also keeps you from having to remember to put your current working code in your PYTHONPATH. It’s just a really friendly option for easy_install that will make your life just a little easier. Thanks, PJE!