In message <mailman.2365.1256979069.2807.python-l...@python.org>, Albert Hopkins wrote:
> On Sat, 2009-10-31 at 21:32 +1300, Lawrence D'Oliveiro wrote: > >In message <6e603d9c-2be0-449c-9c3c-bab49e09e...@13g2000prl.googlegroups.com>, >Carl Banks wrote: > >> 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? > > I think as someone pointed out earlier, in Unix-like operating systems, > a "regular" library's file name starts with "lib", e.g. libcrypt.so. So > this would not conflict with Python's crypt.so. I just checked my Debian installation: l...@theon:~> find /lib /usr/lib -name \*.so -a -not -name lib\* -print | wc -l 2950 l...@theon:~> find /lib /usr/lib -name \*.so -print | wc -l 4708 So 63% of the shareable libraries on my system have names NOT beginning with lib. Any better theories? -- http://mail.python.org/mailman/listinfo/python-list