From: Jean-Paul C. <ex...@di...> - 2009-04-21 18:27:37
|
On Tue, 21 Apr 2009 10:58:41 -0700, patrick flaherty <pa...@we...> wrote: > >well dumpbin recognizes, say, ssl.pyd as a to-at-least-some-extent >well-formed DLL. > > > C:\Python26\Lib\site-packages\OpenSSL>dumpbin ssl.pyd > > Microsoft (R) COFF/PE Dumper Version 9.00.21022.08 > > Copyright (C) Microsoft Corporation. All rights reserved. > > > > > > Dump of file ssl.pyd > > > > File Type: DLL > > > > Summary > > > > 1000 .bss > > 4000 .data > > 1000 .edata > > 2000 .idata > > 2000 .rdata > > 1000 .reloc > > 4000 .text > > > > C:\Python26\Lib\site-packages\OpenSSL> > >But even when I put the prebuilt ( the pyopenssl-win download ) >module into place, the DLLs (not unsurprisingly) refused to import. > >So how does this work and what's the problem? Windows is still largely a mystery to me, so I can't tell you how it works. I do think that I understand the problem, which is that the OpenSSL library isn't being found by Windows. The pyOpenSSL library ssl.pyd is linked against it. Since you said you already have the OpenSSL libraries in the Python libs directory, I'm not sure why it's not being found. Jean-Paul |