In a basic test where all I do is:
import sys
Response.Write(sys.version)
It loads the following dlls:
c:\windows\wow64\python27.dll
c:\windows\wow64\pywintypes.dll
c:\windows\wow64\pythoncomloader.dll
c:\windows\pythoncom27.dll
It loads the following extensions:
c:\python27\lib\site-packages\
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 f
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
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.
>
> Chri
On Tue, Sep 13, 2011 at 11:45 AM, Chris Lambacher
wrote:
> 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?
>
Scratch that theory. This extension has a manifest with ms
On 11/09/2011 9:20 AM, Chris Lambacher wrote:
On Sun, Sep 11, 2011 at 11:57 AM, Chris Lambacher
wrote:
If so, that surprises me. To get as far as you did, much of the pywin32
framework was imported, so all those modules must have imported OK.
I don't know why the imported pyd files are not
On Sun, Sep 11, 2011 at 11:57 AM, Chris Lambacher
wrote:
>>
>> If so, that surprises me. To get as far as you did, much of the pywin32
>> framework was imported, so all those modules must have imported OK.
>
> I don't know why the imported pyd files are not picking up the version
> from pythoncom
On Thu, Sep 8, 2011 at 11:24 PM, Mark Hammond wrote:
> I guess you are saying that that module will have no reference to the CRT
> assembly and that you will rebuild it so it does and that will fix the
> problem?
I am rebuilding to ensure that the CRT reference is included in the
DLL manifest for
Hi Chris,
I was wondering if you are missing this DLL:
msvcr90.dll
It is absent in most builds unless you insure it gets put in. I can't
remember the documentation on it, but doing a search and you will get a lot of
responses on Google.
Bruce
Re: Loading C extensions in Python
On 9/09/2011 12:58 PM, Chris Lambacher wrote:
Hi Mark,
It is not Wow64. I did a very basic test to see what I get. I
installed 2.7.2 x64 and appropriate pywin32 216, and lxml 2.3, throw:
import sys
Response.Write(sys.version)
import lxml.etree
Response.Write("
Worked")
into an ASP file and
Hi Mark,
It is not Wow64. I did a very basic test to see what I get. I
installed 2.7.2 x64 and appropriate pywin32 216, and lxml 2.3, throw:
import sys
Response.Write(sys.version)
import lxml.etree
Response.Write("
Worked")
into an ASP file and get:
2.7.2 (default, Jun 12 2011, 14:24:46) [M
Hi Mark,
I make changes to *other* extensions. I documented the change I made
to distuils here:
http://groups.google.com/group/isapi_wsgi-dev/msg/aa11ed3058e73660
Basically I disable the step that filters the MSVCRT out of the
manifest. And then re-build the extension. I have not yet ventured
int
On 7/09/2011 12:56 PM, Chris Lambacher wrote:
Hi Mark,
It looks like it is trying to use pythoncomloader26.dll. Maybe it is
to due with the Wow64 stuff? I've pasted the Registry values below in
case you can get any insight into it. If you have any suggestions
about how to go about debugging it.
I can also confirm that pythoncomloader26.dll has a manifest that
includes the MSVCRT as Microsoft.VC90.CRT.
-Chris
On Tue, Sep 6, 2011 at 10:56 PM, Chris Lambacher wrote:
> Hi Mark,
>
> It looks like it is trying to use pythoncomloader26.dll. Maybe it is
> to due with the Wow64 stuff? I've past
Hi Mark,
It looks like it is trying to use pythoncomloader26.dll. Maybe it is
to due with the Wow64 stuff? I've pasted the Registry values below in
case you can get any insight into it. If you have any suggestions
about how to go about debugging it. I am happy to put a little effort
in here on my
On 7/09/2011 5:17 AM, Chris Lambacher wrote:
Hi,
Whenever I load an extension using the ActiveX Script for Python in a
Classic ASP page, I get an error saying the DLL can't be loaded. I
have solved this problem thus far by patching the distutils source for
my local Python instance and rebuilding
Hi,
Whenever I load an extension using the ActiveX Script for Python in a
Classic ASP page, I get an error saying the DLL can't be loaded. I
have solved this problem thus far by patching the distutils source for
my local Python instance and rebuilding the extension (see
http://groups.google.com/gr
16 matches
Mail list logo
