Mark Hammond wrote:
>
> What happens if you give that executable a manifest referencing the CRT?
> Note that things changed since pywin32 build 214 - now (almost) none
> of the pywin32 pyd files have a manifest at all, meaning they can be
> loaded correctly by Python itself in all cases - but t
On 2/02/2011 3:11 AM, Tefnet Developers wrote:
Dnia 2011-02-01, wto o godzinie 10:44 +1100, Mark Hammond pisze:
This stuff is painful and poorly documented. Is it possible the code
which triggers the failing import is on a different thread than the one
which loaded Python? If so, I suspect the
On Tue, Feb 01, 2011, Tefnet Developers wrote:
>
> $ make pytest.exe
> i586-mingw32msvc-gcc -I./include -I./include/python -Wall -pedantic
> -std=c99-c -o pytest.o pytest.c
> i586-mingw32msvc-gcc -L./lib -o pytest.exe pytest.o -lmingw32 -lpython26
> rm pytest.o
>
> The output looks like this:
Dnia 2011-02-01, wto o godzinie 10:44 +1100, Mark Hammond pisze:
> This stuff is painful and poorly documented. Is it possible the code
> which triggers the failing import is on a different thread than the one
> which loaded Python? If so, I suspect the magic done by Python in
> dl_nt.c may no
Dnia 2011-02-01, wto o godzinie 10:44 +1100, Mark Hammond pisze:
> This stuff is painful and poorly documented. Is it possible the code
> which triggers the failing import is on a different thread than the one
> which loaded Python?
I have added a little thread id reporting function:
static v
This stuff is painful and poorly documented. Is it possible the code
which triggers the failing import is on a different thread than the one
which loaded Python? If so, I suspect the magic done by Python in
dl_nt.c may not be kicking in, which is supposed to ensure all python
modules are load
