Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #108541 > unrolled thread

Re: Finding .so files without setting LD_LIBRARY_PATH

Started bydieter <dieter@handshake.de>
First post2016-05-12 09:08 +0200
Last post2016-05-12 09:08 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Finding .so files without setting LD_LIBRARY_PATH dieter <dieter@handshake.de> - 2016-05-12 09:08 +0200

#108541 — Re: Finding .so files without setting LD_LIBRARY_PATH

Fromdieter <dieter@handshake.de>
Date2016-05-12 09:08 +0200
SubjectRe: Finding .so files without setting LD_LIBRARY_PATH
Message-ID<mailman.603.1463036926.32212.python-list@python.org>
Paul Smith <paul@mad-scientist.net> writes:
> ...
> That works fine, but here's the problem: because LD_LIBRARY_PATH is in
> Python's environment it is also passed down to programs invoked by
> Python.  That means if I (for example) invoke subprocess.call(['ssh',
> ...]) then it fails because the system ssh is looking for the system
> libcrypto.so, and when it finds the Python libcrypto.so instead
> (because of LD_LIBRARY_PATH) it fails.

I have had a similar problem - however with "PYTHONPATH" instead
of "LD_LIBRARY_PATH". I solved it by removing "PYTHONPATH" from
"os.environ" during Python startup. This way, the envvar
"PYTHONPATH" was effective to set up "sys.path" but
processes started from this python would not see it.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web