- Compile and install a stock
python from scratch, somewhere into your usual use account
(using $HOME/python as a
prefix, or something similar).
- Temporarily change your PATH
so that the newly installed python interpreter is
found
- Install adesklets in the same
way inside your account (modified prefix at configuration
time). Since you pointed adesklets to your "private" python
environment, the module will be installed there.
- Trash the temporary
PATH. but always launch
adesklets using something similar too:
env - PATH=$HOME/python/bin:$PATH adesklets
This way, you can have adesklets using the private,
gc-correct interpreter, and still use the system-wide patched
one for the rest. Of course, many variant of this are also
possible, like sticking a
$HOME/bin in your PATH at login time,
and put in it a wrapper adesklets script in place that mangle
path in the way described above... But you get the idea.
Yours,