Python libs on Windows ME
thomas at jollybox.de
Tue Aug 31 23:04:56 CEST 2010
On Tuesday 31 August 2010, it occurred to hexusnexus at gmail.com to exclaim:
> I'm not guessing that this is a problem on Windows 98, but on Windows
> ME modules in /Lib don't seem to load. Examples include site.py and
> os.py which are both located in the top level Lib directory. The same
> thing happens with Python 2.3, 2.4, and 2.5. I can't get IDLE to load
> and the Python interpreter always complains that it can't load the
> "site" module even if Python is run from the same directory as the
> module (note: this does not happen if a module is loaded from the
> current working directory while in the interpreter).
What is sys.path set to ?
python.exe -c "import sys; print(sys.path)"
It sounds like the stdlib directory is not on sys.path. Couldn't say why
> I would use another os like Linux or Windows 2000, but this particular
> computer can't even seem to handle even the most minimal graphical
> Linux distributions.
Really? I'm sure you can get Linux on there somehow. It might not be trivial,
but it should definitely be possible. Out of interest: what distros did you
More information about the Python-list