Egg problem (~/.python-eggs)

[Damjan]

>> I'm trying to install a program that uses Durus on a server.  It
>> appears that if a Python program uses eggs, it creates a
>> ~/.python-eggs/ directory, so the home directory must be writeable.
>> This conflicts with server environments where you want to run a daemon
>> with minimum privileges.  Second, it appears to use the real user ID
>> rather than the effective user ID to choose the home directory.  In
>> this case I'm trying to use start-stop-daemon on Linux to start my
>> Python program, switching from user 'root' to user 'apache'.
> 
> I solved the immediate problem by reinstalling Durus as a directory egg
> rather than a compressed egg.  So is the answer just not to use
> compressed eggs?

If the .egg file contains binary modules, those must be unpacked out of
the .egg (a Zip file actually) so that the kernel/lib-loader can map them.
If your .egg package doesn't have any binary modules, then it doesn't need
to unpack anything.


-- 
damjan