On Thursday, May 12, 2016 at 9:51:02 AM UTC+12, Paul Smith wrote:
> ... 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 sy
On Thu, 2016-05-12 at 07:55 +0300, Jussi Piitulainen wrote:
> eryk sun writes:
>
> > On Wed, May 11, 2016 at 10:39 PM, Paul Smith wrote:
> > > Hi all. I have a locally-built version of Python (2.7.11) that I'm
> > > copying around to different systems, running all different versions of
> > > GNU/
Paul Smith 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
eryk sun writes:
> On Wed, May 11, 2016 at 10:39 PM, Paul Smith wrote:
>> Hi all. I have a locally-built version of Python (2.7.11) that I'm
>> copying around to different systems, running all different versions of
>> GNU/Linux.
> ...
>> What I'd like to do is have a way of setting the library pa
On Wed, May 11, 2016 at 10:39 PM, Paul Smith wrote:
> Hi all. I have a locally-built version of Python (2.7.11) that I'm
> copying around to different systems, running all different versions of
> GNU/Linux.
...
> What I'd like to do is have a way of setting the library path that
> Python uses whe
Hi all. I have a locally-built version of Python (2.7.11) that I'm
copying around to different systems, running all different versions of
GNU/Linux. Because I need this to work across systems I'm bundling
important .so's with my Python installation (libcrypto, libssl,
libreadline, libgmp) which a
