2.5a1 import of .dlls

[sven.nystrom]

I've re-built an extension module (as a .dll) using the 2.5a1 release.
Unexpectedly, I'm not able to simply import it (not the way I can when
building it for 2.3). Using imp.load_dynamic() the import succeeds.

import minx # Implemented in a .dll - fails Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named minx import imp # Workaround
import os
minx = imp.load_dynamic('minx', os.getcwd() + '\\minx.dll')

I couldn't find anything to indicate this is by design in 2.5a1 (I did
read the PEP 328: Absolute and Relative Imports) - am I doing something
wrong?

[Thomas Heller]

sv**********@gmail.com wrote:

I've re-built an extension module (as a .dll) using the 2.5a1 release.
Unexpectedly, I'm not able to simply import it (not the way I can when
building it for 2.3). Using imp.load_dynamic() the import succeeds.

import minx # Implemented in a .dll - fails Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named minx import imp # Workaround
import os
minx = imp.load_dynamic('minx', os.getcwd() + '\\minx.dll')

I couldn't find anything to indicate this is by design in 2.5a1 (I did
read the PEP 328: Absolute and Relative Imports) - am I doing something
wrong?

Extension modules for 2.5 can no longer have the '.dll' extension, they must
have a '.pyd' extension. I don't know why this isn't documented somewhere (although
I would expect it in Misc/NEWS instead of in PEP 328) - you should filke a bug report.

Thomas