[bf1942] Using sqlite with BF2 in Windows

["Einar S. Idsø"]

Hi again,

On my path to circumventing this problem, I am working on an XML-parser.
But using xml.dom.minidom causes a similar problem to what I had for
sqlite. Here's an excerpt from my code:

from xml.dom import minidom
(...)
minidom.parseString(cmd)

The last line fails with the exception "exceptions.ImportError". This is
on a Linux host. I've tried the same in a regular python interpreter,
and it works fine.

It seems as if xml.dom.minidom.parseString uses
xml.dom.expatbuilder.parseString which uses xml.parsers.expat which in
turn depends on pyexpat which doesn't exist. Is there any way to get
that missing module into the internal py-engine for the next patch?

I'd rather not be handling xml with plain regexps, and the deprecated
xmllib package gives me the shivers...

Cheers,
Einar


Andreas Fredriksson wrote:
> On 4/10/06, "Einar S. Idsø" <esi at itk.ntnu.no> wrote:
> 
>>The OS lib is just as crippled in Lin as it is in Win, isn't it? I don't
>>see how importing sqlite would be affected by the os lib; could you
>>elaborate?
> 
> 
> I think the import hooks were changed on win32 so that DLLs are never
> loaded. I don't remember the exact reason but most likely it was to
> avoid backdoors (e.g. DLLInit) that would install and tamper with BF's
> code without alarming PunkBuster on the client side.
> 
> I believe the change in question is entirely in the win32 import
> implementation (the DLL resolver). Almost all extensions are
> statically linked to the shipped DLL rather than kept outside in
> separate DLLs.
> 
> Hope this helps to clarify the situation,
> 
> // Andreas
> 
> --
> Those who live by the sword get shot by those who don't.
>