My reading of the Python 2.6.1 version of dynload_win.c tells me that:
1. It uses LoadLibraryEx() to attempt to load the pyd given its full
pathname
2. If that fails, it gets the Windows error code using GetLastError()
3. It gets the Windows message text using FormatMessage()
4. It assembles
Mark Hammond wrote:
On 23/02/2009 11:41 PM, Chris Cormie wrote:
If that not-very-technical description [all I've ever needed] doesn't
help, you'll need to read the DW help file (HTFF1K) or wait till
someone who knows what they are doing comes along :-)
LOL, I am that person
John Machin wrote:
On Feb 23, 11:41 pm, Chris Cormie wrote:
If that not-very-technical description [all I've ever needed] doesn't
help, you'll need to read the DW help file (HTFF1K) or wait till
someone who knows what they are doing comes along :-)
LOL, I am that person
Gabriel Genellina wrote:
En Mon, 23 Feb 2009 10:41:20 -0200, Chris Cormie
escribió:
If that not-very-technical description [all I've ever needed] doesn't
help, you'll need to read the DW help file (HTFF1K) or wait till
someone who knows what they are doing comes along :-)
Mark Hammond wrote:
On 23/02/2009 11:41 PM, Chris Cormie wrote:
If that not-very-technical description [all I've ever needed] doesn't
help, you'll need to read the DW help file (HTFF1K) or wait till
someone who knows what they are doing comes along :-)
LOL, I am that person
If that not-very-technical description [all I've ever needed] doesn't
help, you'll need to read the DW help file (HTFF1K) or wait till
someone who knows what they are doing comes along :-)
LOL, I am that person :p
Your technique works well and it does provide the information and it is
a (roun
Hi,
I've been Googling around on a moderately common Windows Python problem:
a mismatch between the symbols a python extension thinks are available
and the contents of the associated DLL. Python users running into this
problem are greeted with:
import
"ImportError: DLL load failed: The spec
