On Sun, Mar 20, 2011 at 1:48 PM, Leonardo Rochael Almeida <leoroch...@gmail.com> wrote: > It's likely that pythonv shoudn't do anything differently, at least > from the POV of the Python binary. I just wanted to mention a use-case > for needing LD_LIBRARY_PATH set while running Python.
I'd agree that for the use-cases I've dealt with, it's not clear that pythonv in particular should be responsible for handling LD_LIBRARY_PATH; it would at times be convenient, but not essential. Existing workarounds would still apply, and in some cases would still be necessary. There are two primary changes we've wanted to make when the Python process is started: - setting environment variables that have to be set for the dynamic loaded (LD_LIBRARY_PATH is the most common), and - running as a particular user. Both of these would require restarting Python to get set up, and neither is part of getting the basic "virtual" environment set up. Getting environment changes made & restarting the interpreter wouldn't solve both of these, and the run-as-user behavior is definitely inappropriate for a basic pythonv behavior. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> "A storm broke loose in my mind." --Albert Einstein _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
