Hi Tzahi,
as it usually happens Language Connectors are proud to report
obscure and meaningless diagnostic messages when some failure
is encountered.
Python doesn't seems to be the expect ion to the rule:
> "A dynamic link library (DLL) initialization routine failed."
>
note: the name of the failing DLL is a secret mystery :-P
anyway, we can get few useful bits of information out of this:
1. sqlite do actually started the "load_extension" sequence;
well, so it's for sure a supported option.
2. mod_spatialite.dll was successfully located within the
system path; otherwise a "module not found" message (or
something like) should be reported.
3. anyway the DLL failed to correctly load.
AFAIK there are only two possible explanations for this:
a. the DLL depends on soma other DLL(s) and one of them
cannot be loaded: we can reasonably exclude this
hypothesis because sqlite3.exe successfully loads the
extension.
b. the DLL has the wrong addressing mode: i.e. an invalid
attempt was made by a 32 bit application to load a 64
bit DLL (or the opposite).
are you really sure that your Python exactly matches
the addressing mode of the DLLs ?
bye sandro