Compiled Win32 modules should have .pyd extension

Bug #333621 reported by blackdaemon
2
Affects Status Importance Assigned to Milestone
Enso Project
Fix Committed
High
blackdaemon

Bug Description

 Reported by unfocused, Mar 21, 2008

What steps will reproduce the problem?
1. Compile win32 backend
2. Run with Python 2.5
3. Imports of compiled modules fail

Python v2.5 on Windows will no longer import modules with the .dll
extension - they need to have the .pyd extension instead.

Thankfully, SCons allows you to easily override the extension for the
output of SharedLibary, via SHLIBSUFFIX

At the moment, this is restricted to:
* the Swig helper script win32/SConsTools/SwigTool.py
* the Cairo build script win32/src/Graphics/cairo/src/SConscript

Quote from Python.org:

Windows: .dll is no longer supported as a filename extension for extension
modules. .pyd is now the only filename extension that will be searched for.

See: http://docs.python.org/whatsnew/ports.html#SECTION0001510000000000000000

Related branches

Revision history for this message
blackdaemon (blackdaemon) wrote :
Revision history for this message
blackdaemon (blackdaemon) wrote :

Above patch has been provided by Unfocused

Revision history for this message
blackdaemon (blackdaemon) wrote :

Comment 1 by zelexi, May 01, 2008

Just changing those two files doesn't work for me. Are you sure those are the only
changes necessary to accomidate Python 2.5?

Changed in enso:
assignee: nobody → blackdaemon
importance: Undecided → High
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.