Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder2.hal-mli.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Wed, 23 Jan 2013 18:43:50 -0800 (PST)
In-Reply-To: <mailman.908.1358958543.2939.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=183.221.13.237; posting-account=C5ZW1goAAABBiDY20ieZObmqNJVCIaGw
References: <552da0d2-e744-4ce2-8204-14a7274515de@googlegroups.com> <mailman.908.1358958543.2939.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Failed to import a "pyd: File When python intepreter embed in C++	project
From: Junze Liu <liujz39@gmail.com>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "python-list@python.org" <python-list@python.org>
Precedence: list
Message-ID: <mailman.940.1358995439.2939.python-list@python.org>
Lines: 86
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:37532

On Thursday, January 24, 2013 12:28:58 AM UTC+8, Leonard, Arah wrote:
> > I create a pyd File named "testPyd" with boostPython,and then I import =
the testPyd module into "test.py", it works perfect!
>=20
> > But when I embeded the python interpreter into my C++ project and run t=
he "test.py", it comes out a "ImportErr: no module named testPyd".
>=20
> > It has confused me for two days and I googled for long time,but I can't=
 find the answer!
>=20
> > Anybody here can help me ?
>=20
> > Thank you!
>=20
> >=20
>=20
>=20
>=20
> 	Ah, that sounds familiar.  I have a small bit of experience with Boost. =
 I could be wrong, because once you start mixing it up with Boost all sorts=
 of weird things can happen (especially on a MS compiler, because no one te=
sts for Windows, let alone a pay-for compiler) but my experience has shown =
that if you get that specific import error, what it actually means is just =
that the PYD import failed for ANY reason.  It has nothing to do with the n=
ame or that the PYD couldn't be found.  Just that somewhere, at some time d=
uring import, it failed to fully load.
>=20
>=20
>=20
> 	In my use a lot of times it was either that a DLL that module depended o=
n wasn't in the path, or my favorite kicker, that some compile/link flags b=
etween the PYD and the Python interpreter don't match well enough.  (Usuall=
y from mixing debug and release builds together.)
>=20
>=20
>=20
> 	From what I've seen anyway, the Python interpreter really doesn't like b=
eing built in a traditional debug mode, so I always do a release build of i=
t.  It's a little inconvenient, but in the linker flags you can still set y=
our PYDs to generate debug information even in release builds, so you can s=
till run the debugger on them when you attach to the process of the python =
interpreter EXE.  And especially be sure to use the RELEASE runtime library=
 flag (such as /MD) instead of the debug flag (such as /MDd).
>=20
>=20
>=20
> 	That's as much as I know anyway.  Though depending, if you add any new t=
emplates/libraries into Boost (such as for NumPy ndarray), you also may nee=
d to use the /DBOOST_ALL_NO_LIB compiler macro on an MS compiler because MS=
 doesn't adhere to template standards correctly and you often end up with m=
ultiply-defined functions if you don't use that macro.  If I remember corre=
ctly.  (It's been a while.)
>=20
>=20
>=20
> 	That and you may be picking up variable length arrays out of your teeth,=
 replacing chunks of code with the use of new and delete operators.  No one=
 tests for Microsoft and the MS compiler is way behind in adhering to C/C++=
 standards, and VLAs pop up a lot.
>=20
>=20
>=20
> 	Hopefully something in all of this helped.  Boost can be ... daunting.  =
I get it, in theory.  But in practice it often hurts my head.  ;)
>=20
>=20
>=20
> Sincerely,
>=20
> Arah Leonard

Dear Lenoard,
    Thanks for your hearty assistance, and it finally works.I just change m=
y RELEASE Run Time Library flag to MD, then the results come out.
    Before I receive your mail, I googled for kinds of solutions and tried =
to solve this problem, but none of them works.Yesterday, someones said that=
 the python module in *pyd Files* should be initialized before they can be =
embed into C++, and a function named init<ModuleName> should be called befo=
re importing the module, I was confused with this for a couple of hours unt=
il I saw your mail.
   I am new to boost.python.If I propose any questions that seems naive to =
you the other days, any suggestion from you would be more than welcome! =20
   Thanks again for your help to make me out of my wrong way!

Sincerely,
George Liu