By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,813 Members | 1,130 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,813 IT Pros & Developers. It's quick & easy.

Pythonwin not loading DLL, should I change extensions by .pyo or pyd?

P: n/a

Python 2.5 doesn't support/load .dll anymore. Is PythonWin 2.5 the
same case?

If a .DLL file is not loading, should I change its extension for it to
work?
What extensions should be now, .pyo, .pyd, etc? which one?
What is the meaning of each extension?

Thanks,
Angelica E-G.
Nov 17 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
En Mon, 17 Nov 2008 13:01:11 -0200, Pekeika
<m.*****************@umiami.eduescribió:
Python 2.5 doesn't support/load .dll anymore. Is PythonWin 2.5 the
same case?

If a .DLL file is not loading, should I change its extension for it to
work?
What extensions should be now, .pyo, .pyd, etc? which one?
What is the meaning of each extension?
Python supports being extended using "extension modules"; on Windows they
are dynamic libraries (DLL). Before 2.5, the extensions ".dll" and ".pyd"
were both valid; starting with 2.5, only files ending in ".pyd" are
recognized.
Note that this applies to extension modules *only*, not generic DLLs.
All binary packages targeted to 2.5 use the right name for their extension
modules, at least all that I know of. You don't have to rename anything.

A .pyo file is a totally different thing; it's a compiled Python source
(like a .pyc) but with optimization turned on.

--
Gabriel Genellina

Nov 17 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.