Rebooting the thread...
While testing mxNumber, I discovered what looks like a bug in Win95: both Thomas Heller and I are seeing a problem with Python 2.1 when importing extension modules which rely on other DLLs as library.
Interestingly, the problem only shows up when starting Python from the installation directory. Looking at the imports using python -vv shows that in this situation, Python tries to import modules, packages, extensions etc. using *relative* paths.
Now, under Win98 there is no problem, but Win95 doesn't seem to like these relative imports when it comes to .pyd files which reference DLLs in the same directory. It doesn't have any problems when Python is started outside the installation dir, since in that case Python uses absolute paths for importing modules and extensions.
Would it be hard to tweak Python into always using absolute search paths during module import ?