Maintaning local changes

[Martin (gzlist)]

2009/8/26 Ivan Sagalaev <maniac at softwaremaniacs.org>:
>
> The only (inconvenient) solution that I can think of is to have one local
> branch dedicated to testing that will contain those environment
> modifications. Then I do development in other branches and every time I need
> to test my work I merge it to this test branch, test it and revert it back
> to "upstream state + environment mods" every time.

The way I hacked around this very problem for working on bzr itself
was to write a small wrapper script around setup.py that made it easy
to switch my site-packages bazaar to different branches.

It's very low-end solution, it basically:
* Uninstalls the current bzr
* Asks which branch to use
* Applies a patch of local changes all branches will want
* Runs setup.py
* Applies the patch again in reverse

> Is there a better solution?

Doubt you could count this as a better way, but it was less effort
than working with distutils or trying to upstream hacks around python
2.4 only corner cases.

Martin