Error with PIL & Portable Python

[Eloque]

Now this might be due to some configuration issues or another, but I
cannot find a fix for it, and as such, I thought I'd post it.

In short, when I try to use the PIL stuff in the PP 2.6 edition I get
this, well known, error:

"The _imaging C module is not installed"

I tracked it down somewhat further and couldn't find anything. The
code works fine on the non-portable Pythons I have. It's just the
import of the PIL.

Reinstalling, rebuilding or up- downgrading the PIL modules doesn't
help, it happens only on my WinXP boxes, not on my Vista boxes, also,
it happens only with the 2.6 edition, not the 2.5 one.

The error is explained here : http://effbot.org/zone/pil-imaging-not-installed.htm

But no solution is given. It loads everything fine, but the _imaging
module. But, profiling shows that when Image is imported, it actually
runs into an error as well, something about a missing manifest and a
"missing export in a delay-load dependent module"

The full error I get when I profile:

Loaded "_IMAGING.PYD" at address 0x00DB0000. Successfully hooked
module.
LDR: LdrpWalkImportDescriptor() failed to probe h:\pa\portableapps
\portablepython_1.1_py2.6.1\app\lib\site-packages\PIL\_imaging.pyd for
its manifest, ntstatus 0xc0150002
Unloaded "_IMAGING.PYD" at address 0x00DB0000.
LoadLibraryExA("h:\pa\portableapps\portablepython_1.1_py2.6.1\app\lib
\site-packages\PIL\_imaging.pyd", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) returned NULL. Error: (14001).

Don't know if it's anything particular with PP, (awesome stuff btw)
but I tought I'd inform you anyways.

regards
E

[Perica Zivkovic]

Hi there,

thanks for this detailed error report. I created an high priority
issue on the project portal so we can track this - http://portablepython.com/ticket/9

Will look into it as soon as I find time for it. On the first look
smells like PIL for py 2.6 CRT problem.

keep pythoning!

Perica

[Eloque]

No problem, thanx for putting it on the list.

Another thing I did find, some suggested that it is due to the fact
the the PIL and Python bins are compiled with different compilers or
such. Something to do with Visual C version 2008 vs. 2003, but I can't
find much more yet.

Thanx for the work on PP

E

On Sep 17, 8:11 pm, Perica Zivkovic <perica.zivko...@gmail.com> wrote:
> Hi there,
>
> thanks for this detailed error report. I created an high priority

> issue on the project portal so we can track this -http://portablepython.com/ticket/9

[Perica Zivkovic]

Thats the CRT I'm mentioning. It is Microsoft C Runtime (http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.80).aspx) I guess py 2.6 is compiled against one version and PIL against another. With PP CRT is included but only version needed for python.exe. If PIL uses another version and you don't have it installed on your XP box then it will not work.

What we need to find out is against which version is PIL built and you can do it with depends.exe tool which comes with installation of visual studio 2005.

cheers,

Perica

[Eloque]

I don't have VS2005 installed, I'll look for some way to obtain it.

regards
E

On Sep 18, 7:19 am, Perica Zivkovic <perica.zivko...@gmail.com> wrote:
> Thats the CRT I'm mentioning. It is Microsoft C Runtime (http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.80).aspx) I guess py 2.6
> is compiled against one version and PIL against another. With PP CRT is
> included but only version needed for python.exe. If PIL uses another version
> and you don't have it installed on your XP box then it will not work.
> What we need to find out is against which version is PIL built and you can
> do it with depends.exe tool which comes with installation of visual studio
> 2005.
>
> cheers,
>
> Perica
>