I don't import anything from pywin32 other than what would have already been loaded before getting to my code by the pywin32 machinery that makes active scripting work. When I get back to my computer I'll look at what gets loaded in the most basic app and try to determine what loads those modules first.
-Chris On Tuesday, September 13, 2011, mhamm...@skippinet.com.au < mhamm...@skippinet.com.au> wrote: > But none of pywin32, right? So the obvious question is still how those other modules differ from pywin32 > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > Chris Lambacher <ch...@kateandchris.net> wrote: >> >> Basically every C extension I have ever tried: >> >> lxml >> pycrypto >> pyodbc >> psyco >> >> -Chris >> >> On Tue, Sep 13, 2011 at 1:30 PM, mhamm...@skippinet.com.au >> <mhamm...@skippinet.com.au> wrote: >> > What are the other modules? Is it just the etree one? >> > >> > Mark >> > -- >> > Sent from my Android phone with K-9 Mail. Please excuse my brevity. >> > >> > Chris Lambacher <ch...@kateandchris.net> wrote: >> >> >> >> On Sun, Sep 11, 2011 at 3:42 PM, Mark Hammond < mhamm...@skippinet.com.au> >> >> wrote: >> >> > The best I can suggest is to make a small .asp example which requires >> >> > nothing beyond pywin32 - eg, some of the asp samples. Once you are >> >> > convinced that works, I'd start looking into what is different about the >> >> > lxml.etree >> module - I suspect you will find that module references the >> >> > CRT >> >> > assembly. >> >> > >> >> >> >> I was looking at something else in Process Explorer and noticed a pyd >> >> that was loaded in the standalone part of the app that I did not >> >> rebuild and wondered if it loaded correctly in the ASP app. In this >> >> case it was the _speedups.pyd extension of the markupsafe package and >> >> indeed when I look at the running w3p.exe process, I see the >> >> _speedups.pyd extension is loaded and modifying my test app to load >> >> the _speedups.pyd module and >> >> everything works. >> >> >> >> Maybe the other modules are loading other DLLs and therefore need the >> >> manifest in order to be able to inherit it since it is not the main >> >> process loading the DLLs anymore? >> >> >> >> -Chris >> >> >> >> >> >> -- >> >> Christopher Lambacher >> >> ch...@kateandchris.net >> > >> >> >> >> -- >> Christopher Lambacher >> ch...@kateandchris.net <ch...@kateandchris.net> > -- Christopher Lambacher ch...@kateandchris.net
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
