I am working with a code that has python embedded in it. The embedded python points to my local python. Outside of the embedding application, I can import a third part module (wrapped ITK). When, I attempt to import the same module from within the embedding application, it fails with the message 'possible version mismatch'. Also, this module was built against my local python. In short, there can be no version mismatch because it is all the same pyhton.

Can anyone shed some light on this?

I do not know much about the embedding of python. In my case, I do know that the libpython23.a and libnumeric.a libraries are somehow involved. These may be the culprits as I need to include particular version in my build. Again, any light to be shed?

Thanks so much


Daniel R Einstein, PhD
Biological Monitoring and Modeling
Pacific Northwest National Laboratory
P.O. Box 999; MSIN P7-59
Richland, WA 99352
Tel: 509/ 376-2924
Fax: 509/376-9064
daniel.einstein at pnl.gov

From http Sun Aug 21 04:39:56 2005
From: http (Paul Rubin)
Date: 20 Aug 2005 19:39:56 -0700
Subject: global interpreter lock
References: <mailman.3258.1124442762.10512.python-list@python.org>
<7xvf2183mt.fsf@ruckus.brouhaha.com> <1124553656.678727@yasure>
Message-ID: <7xiry0vwqr.fsf@ruckus.brouhaha.com>

Mike Meyer <mwm at mired.org> writes:
Even simpler to program in is the model used by Erlang. It's more CSP
than threading, though, as it doesn't have shared memory as part of
the model. But if you can use the simpler model to solve your problem
- you probably should.
Well, ok, the Python equivalent would be wrapping every shareable
object in its own thread, that communicates with other threads through
Queues. This is how some Pythonistas suggest writing practically all
multi-threaded Python code. It does a reasonable job of avoiding
synchronization headaches and it's not that hard to code that way.

But I think to do it on Erlang's scale, Python needs user-level
microthreads and not just OS threads. Maybe Python 3000 can add some
language support, though an opportunity was missed when Python's
generator syntax got defined the way it did.

I've been reading a bit about Erlang and am impressed with it. Here
is a good thesis about parallelizing Erlang, link courtesy of Ulf
Wiger on comp.lang.functional:


The thesis also gives a good general description of how Erlang works.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
postedAug 21, '05 at 2:39a
activeAug 21, '05 at 2:39a

1 user in discussion

Einstein, Daniel R: 1 post



site design / logo © 2022 Grokbase