Although I agree in principle with trying to keep to absolute path names on
sys.path, '.' and a couple of others are sort-of special cases.
But anyway, problem is, Python goes and sticks '.' and "..\lib" on the path
for you when it starts up. I could remove this from the NT implementation,
but I dont think that is sensible.
I can see your point about the difficulties with resolving absolute paths.
A possible fairly easy solution would be to store the cwd of the process
with the code object when loaded. Then, if a program really needed to know
the absolute file name, it could attempt reconstruction given this.
Most paths can use absolute, but '.' seems to be a problem, and also fairly
necessary, as I _want_ to be able to change directories, and load modules
from there (even though it wont be on the path)
Mark.