[Guido]
No it doesn't. The code in site.py only adds site-packages and site-python when os.sep is '/'. RTSL.
Oops. Missed that.
I don't like that. For one thing, modulo a few platform differences, the same mechanism should work for multi-user Unix and Windows LAN installations. And single- user Windows (I know, redundant, even on NT) should be a degenerate case of the above.
What do you mean by "the same mechanism should work"? The same mechanism for what? Are you talking about sharing the installed files somehow?
In the above, "mechanism" basically meant that which creates sys.path. Basically, this came up for me because in standalone configurations (my Installer again), I have to take complete control of sys.path. After doing so differently on Windows and Linux, I finally realized that I can do it the same way on both. Which makes me question why they are so different.
The .pth files are designed for this. Maybe they haven't been explained as well as they should.
I'd say "badgered" or "browbeaten" instead of "explained" ;-).
Much as I love Mark's stuff (and hesitate to criticize crazy Aussies), I wish there weren't so much special casing here for Windows.
It's not Mark's fault, it's Microsoft's fault. If you don't do things the way MS wants you to, experienced Windows users will gripe, misunderstand what you do, etc.
Even MS doesn't do things the way MS says they want you to. I find MS users equally divided between those who scream bloody murder if you touch the registry, and those who scream if you don't. It's not like *nixen suffer from an excessive degree of conformity in preferred installation procedures, but somehow Python survives there...
And no, I don't have any solutions to this, I'm just griping...
Ditto. Understanding the problems is half of the solution though. The problems seem pretty complex!
Grumpily agreed ;-). - Gordon