Finding .so files without setting LD_LIBRARY_PATH

2016-05-11 Thread Paul Smith
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

Re: Finding .so files without setting LD_LIBRARY_PATH

2016-05-12 Thread Paul Smith
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

python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
Hi all. I need to build my own version of Python on a MacOSX system, and I can't seem to do it successfully. I need to build it with a particular location, etc. and so I can't use Homebrew or whatever: I need to compile it myself from the source tarball. I did look through the Homebrew recipe an

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
Thanks for the response Ned! On Wed, 2013-11-13 at 14:40 -0800, Ned Deily wrote: > There shouldn't be any problems with what you are trying to do. It > works for me with Python 2.7.6 and pycrypto-2.6.1. Some suggestions: > - Avoid --enable-shared on OS X at least initially. There are too > many

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
On Wed, 2013-11-13 at 16:00 -0800, Ned Deily wrote: > > The reason I've set PYTHONHOME is ultimately I need this installation to > > be relocatable. It's going to be shared across lots of different > > systems and they'll have the ability to copy it wherever they want. > > That could be problemat

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-14 Thread Paul Smith
On Wed, 2013-11-13 at 23:06 -0800, Ned Deily wrote: > On Nov 13, 2013, at 17:24 , Paul Smith wrote: > > I'm discovering that this is tricky. I don't want to bring OS wars into > > it, but this kind of thing is so simple and just works on GNU/Linux. I > > guess I

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-15 Thread Paul Smith
On Thu, 2013-11-14 at 10:36 -0800, Ned Deily wrote: > In article <1384442536.3496.532.camel@pdsdesk>, > Paul Smith wrote: > [...] > > By relocatable I mean "runnable from any location"; i.e., not fixed. I > > have a wrapper around the Python executable

Sharing Python installation between architectures

2013-11-15 Thread Paul Smith
One thing I always liked about Perl was the way you can create a single installation directory which can be shared between archictures. Say what you will about the language: the Porters have an enormous amount of experience and expertise producing portable and flexible interpreter installations.

Re: Sharing Python installation between architectures

2013-11-16 Thread Paul Smith
On Fri, 2013-11-15 at 18:00 -0500, Paul Smith wrote: > By this I mean, basically, multiple architectures (Linux, Solaris, > MacOSX, even Windows) sharing the same $prefix/lib/python2.7 directory. > The large majority of the contents there are completely portable across > architectures

grammar (was Re: Automation)

2013-11-16 Thread Paul Smith
On Sat, 2013-11-16 at 10:11 -0500, Roy Smith wrote: > In article , > William Ray Wing wrote: > > > And my personal peeve - using it's (contraction) when its (possessive) > > should have been used; occasionally vice-versa. > And one of mine is when people write, "Here, here!" to signify > agr

Re: Sharing Python installation between architectures

2013-11-17 Thread Paul Smith
On Sat, 2013-11-16 at 19:28 -0500, Paul Smith wrote: > On Fri, 2013-11-15 at 18:00 -0500, Paul Smith wrote: > > By this I mean, basically, multiple architectures (Linux, Solaris, > > MacOSX, even Windows) sharing the same $prefix/lib/python2.7 directory. > > The large maj

Re: Sharing Python installation between architectures

2013-11-17 Thread Paul Smith
On Sun, 2013-11-17 at 10:46 -0500, Paul Smith wrote: > Unfortunately, if you set PYTHONHOME then it's used for both $PREFIX and > $EXECPREFIX without any path probing whatsoever, so PYTHONHOME is > unusable with an installation where you've used different values for > --pr

Re: Logger module in python

2013-12-17 Thread Paul Smith
On Wed, 2013-12-18 at 03:27 +, Mark Lawrence wrote: > On 18/12/2013 03:22, smilesonisa...@gmail.com wrote: > > Hi, > > I am a newbie in python. I am looking for a existing module which I > can import in my program to log the objects to a file? > > > > I know there is a module Data::Dumper in pe

Re: Experiences/guidance on teaching Python as a first programming language

2013-12-17 Thread Paul Smith
On Wed, 2013-12-18 at 01:33 +, Steven D'Aprano wrote: > And "What does 'implementation-specific undefined behaviour' actually > mean in practice?", another common question when dealing with C. Only asked by people who haven't had it explained. There's "undefined behavior", and there's "imple

Can sqlite read gzipped databases?

2007-03-20 Thread Paul Smith
Hi, I'd like to read a series of sqlite database files that have already been gzipped and was wondering if this can be done on the fly. In other words, can I avoid explicitly unzipping the file into another file, but instead get an SQL connection to the zip file either directly (can't see an op