[issue43898] Python fails to import .dylib but works when extension is changed to .so

Ned Deily added the comment: Thanks for the clarification. On most platforms other than Windows, Python expects compiled extension modules (usually written in C or C++) to have an extension of .so. This is true as well on macOS. Typically, extension modules are compiled using Python's Distut

[issue43898] Python fails to import .dylib but works when extension is changed to .so

Ellis trisk-grove added the comment: This is with regards to an python extension written in zig (I believe the same behaviour would occur from C as I am just using Python.h). What happens is when I compile the library on my mac it generates myLibrary.dylib file, when testing with python the

[issue43898] Python fails to import .dylib but works when extension is changed to .so

Ned Deily added the comment: Can you please give a code snippet of the behavior you believe is incorrect? It is not clear to me what you mean by importing a library. -- ___ Python tracker __

[issue43898] Python fails to import .dylib but works when extension is changed to .so

New submission from Ellis trisk-grove : This issue is pretty much summed up by the title. Python does manage to import the library and use it however only when the extension is .so otherwise python cannot find it and fails to import. -- components: macOS messages: 391473 nosy: etriskg