Martin v. Löwis wrote:
> I see three options:
> 1. rename sqlite3 again
> 2. link sqlite3 statically into _sqlite3.pyd
> 3. stop treating .DLL files as extension modules
>
> I'm actually leaning towards option 3: what is the rationale
> for allowing Python extension modules to be named .DLL?
A datapoint specific to OS/2 which probably has little relevance to
Windows or to the specific case at hand:
In order to get the curses_panel module to work, I have to forward the
necessary curses entry points from the _curses module DLL. On OS/2, this
only works for DLLs with the extension .DLL, so I ship _curses.pyd as
_curses.dll.
As a consequence, I can't implement option 3 for the OS/2 port but I can
live with the nasty side-effects given the modest userbase and by
documenting the issue in the port README.
If you can make option 3 work for Windows, then I would do it now during
the alpha to see whether it flushes any problems out.
I must admit to being uncomfortable with including version numbers in
module names, especially when they reflect a version outside the scope
of Python. Ending up with a module name that can match a 3rd party
dynamically linkable file would seem problematic no matter which way you
look at it.
FWIW,
Andrew.
-------------------------------------------------------------------------
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: [EMAIL PROTECTED] (pref) | Snail: PO Box 370
[EMAIL PROTECTED] (alt) | Belconnen ACT 2616
Web: http://www.andymac.org/ | Australia
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
