Are *.pyd's universal?

Carl Banks pavlovevidence at
Sat Oct 31 14:16:23 CET 2009

On Oct 31, 1:32 am, Lawrence D'Oliveiro <l... at geek-
central.gen.new_zealand> wrote:
> In message <6e603d9c-2be0-449c-9c3c-
> bab49e09e... at>, Carl Banks wrote:
> > It's not Python that's the issue.  The issue is that if you have a
> > module with a .dll extension, other programs could accidentally try to
> > load that module instead of the intended dll, if the module is in the
> > current directory or system path.  Modules will sometimes find
> > themselves on the path in Windows, so the fact that Windows performs a
> > library search on the path is quite significant.
> Why is it only Windows is prone to this problem?

Unix doesn't search the executable path or current directory when
loading libraries, which if you would have seen if you hadn't ignored
my original reply.

Carl Banks

More information about the Python-list mailing list