30

I have a Python extension written in C and I wonder if I should use the file extension DLL or PYD under Windows. (And what would I use in Linux?)

Are there any differences (besides the filename)?

I found an unofficial article. Is this the secret of pyc? Why can't I find any official article on this topic?

Mike Pennington
  • 41,899
  • 19
  • 136
  • 174
gecco
  • 17,969
  • 11
  • 51
  • 68

4 Answers4

28

pyd files are just dll files ready for python importing.

To distinguish them from normal dlls, I recommend .pyd not .dll in windows.

Here is the official doc about this issue:

http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll

zchenah
  • 2,060
  • 16
  • 30
  • 1
    it seems that this is not just reccomendable, but obligatory. .DLLs, even with the correct PyInit_ and PyModuleDef's aren't recognised as directly importable (on python <= 3.8), although .so's are fine on linux – David Karla Jan 21 '21 at 10:18
9

According to the Creating Your Own Project step (Step 7 of "The Cookbook Approach") of Building C and C++ Extensions on Windows

The output file should be called spam.pyd (in Release mode) or spam_d.pyd (in Debug mode). The extension .pyd was chosen to avoid confusion with a system library spam.dll to which your module could be a Python interface.

So a .pyd file is just a DLL renamed to save on confusion.

On linux however, speaking from experience it seems that you need to use the .so extension for python dlls. This is just a standard unix shared library. I can't provide a source or reason for why python on linux does not change the file extension, however I can show you how to demonstrate it. At the shell, run the following:

python -vv
>>> import fakemodule

You'll notice that the output shows:

trying /usr/lib/python2.5/site-packages/fakemodule.so

obmarg
  • 9,369
  • 36
  • 59
8

Presuming your Python extension foo is intended to be used as a module, accessible via import foo, you don't need to know what the filename extension should be on what operating system. You just use distutils. You will get a .pyd on Windows, and a .so on Linux etc. Read this documentation.

Update in response to comment by @gecco

import foo is working both both extension types: dll and pyd. The extension does not matter here... :

For me (Python 2.7.1, Windows 7), python -vv shows only pyd, py, pyw and pyc extensions (in that order) being searched. If I have foo.pyd in C:\python27\lib\site-packages, import foo works. If I rename that file to foo.dll, import foo fails.

Xbox One
  • 307
  • 2
  • 13
John Machin
  • 81,303
  • 11
  • 141
  • 189
  • `import foo` is working both both extension types: `dll` and `pyd`. The extension does not matter here... – gecco Dec 15 '11 at 18:52
  • In fact I got something wrong... my fault. Unfortunately I cannot withdraw my down vote. I think I can remove it after you updated your post only... – gecco Dec 15 '11 at 19:45
  • From the official docs linked to in the accepted answer above, it states: "Note that the search path for foo.pyd is PYTHONPATH, not the same as the path that Windows uses to search for foo.dll." – wescpy Apr 21 '13 at 04:16
  • @wescpy: I'm not sure whether you are agreeing or disagreeing with my answer, or even what relevance your comment has ... – John Machin May 05 '13 at 02:51
  • Sorry [John Machin](http://stackoverflow.com/users/84270/john-machin,) my comment was for [gecco](http://stackoverflow.com/users/672848/gecco), not you. It *does* matter what the extension is. – wescpy May 06 '13 at 04:40
3

In Windows you can use *.pyd to be imported directly from Python import foo but for *.dll you should use this:

from ctypes import cdll
#load dll file , the file in the same .py file location or enter the full path
mylib=cdll.LoadLibrary("foo.dll") 
#call a function from this dll (c-ext) 
ReturnedValue=mylib.FunctionName()

If you want to explore what functions are exported in this Dll use this tool

UPDATE: Here's an example using distutils and SWIG to build the extension. Check this article out, it shows many simple examples under Windows and Linux.

AndyG
  • 39,700
  • 8
  • 109
  • 143
Abdurahman
  • 628
  • 8
  • 16
  • You are wrong. DLL's can also be directly imported into Python using the `import` statement. – gecco Dec 15 '11 at 18:46
  • I'm sorry I got something wrong... (see my comment in John Machin's port) my fault.... You were right... Unfortunately I cannot withdraw my down vote. I think I can remove it after you updated your post only... – gecco Dec 15 '11 at 19:46
  • 1
    @gecco no problem. I think this [link](http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll) which CHENZhao posted answers your questions about the difference and about the existence of official article. and also John Machin post helps. so all of your questions seems to be answered!!. check also my updated post. – Abdurahman Dec 16 '11 at 17:56
  • Yes I think that currently CHENZhao is making the race :-) – gecco Dec 16 '11 at 17:58