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 void logThread(const char *where) {
FILE *log = fopen(LOGFILE, "a");
fprintf(log, "pygina thread id @ %s: %d\n", where,
GetCurrentThreadId());
fclose(log);
}
I've put it before each method call and before Py_Initialize, and it all
happens in one thread:
pygina thread id @ WlxNegotiate: 612
pygina thread id @ Py_Initialize: 612
pygina thread id @ WlxInitialize: 612
pygina thread id @ WlxDisplayStatusMessage: 612
pygina thread id @ WlxRemoveStatusMessage: 612
pygina thread id @ WlxDisplaySASNotice: 612
pygina thread id @ WlxRemoveStatusMessage: 612
pygina thread id @ WlxLoggedOutSAS: 612
Should I need to do any linking against msvcr90 if python26.dll is
already linked against it and I am linked to python26.dll?
Thanks,
Filip Zyzniewski
Tefnet
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
