On 11/27/2023 12:49 PM, Marco Atzeri via Cygwin wrote:
On 22.09.2023 08:39, Mesibo Technical via Cygwin wrote:
This issue is about Python on Cygwin not using the recommended module extension.
[cut]
Any idea why Cygwin is using the .dll extension instead of the .pyd
extension as recommended by Python's official documentation?
Additionally, is there a way to know during runtime the specific
extension used by a particular version of Python, without having to
make assumptions based on the system type?
Cygwin is Unix on Windows, so the dll extension is equivalent
to the so extension on Linux/Unix.
I am almost sure that we are not modifying the source code for this specific
issue. But I could be wrong
Allow me to add that Cygwin is not a virtual machine in the sense of
WSL (Windows Subsystem for Linux), VirtualBox, etc. Rather, it consists
of a dll library that does a pretty good job mapping POSIX library
functions to Windows ones, and large collections of programs and libraries
that have been ported to the Cygwin environment, including X windows.
In any case, this means that it follows Windows linking conventions and
object formats.
HTH understand why tings are as they are.
Regards - Eliot Moss
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
