Hi,
I'm having trouble in getting Windows absolute paths like e.g d:\foo to work in distutils. They alway seem to be treated as a relative path...
Thanks,
Peter
Peter Bienstman wrote:
Hi,
I'm having trouble in getting Windows absolute paths like e.g d:\foo to work in distutils. They alway seem to be treated as a relative path...
distutils uses Unix path names internally, i.e. / instead of .
On Mon, 15 Apr 2002, M.-A. Lemburg wrote:
Peter Bienstman wrote:
Hi,
I'm having trouble in getting Windows absolute paths like e.g d:\foo to work in distutils. They alway seem to be treated as a relative path...
distutils uses Unix path names internally, i.e. / instead of .
Actually, it's not that simple.
The following works, because setup.py lives in d:\bar
../foo
None of these work:
D:/foo /D:/foo //D:/foo D:\foo \D:\foo \D:\foo
Peter
Peter Bienstman wrote:
On Mon, 15 Apr 2002, M.-A. Lemburg wrote:
Peter Bienstman wrote:
Hi,
I'm having trouble in getting Windows absolute paths like e.g d:\foo to work in distutils. They alway seem to be treated as a relative path...
distutils uses Unix path names internally, i.e. / instead of .
Actually, it's not that simple.
The following works, because setup.py lives in d:\bar
../foo
None of these work:
D:/foo /D:/foo //D:/foo D:\foo \D:\foo \D:\foo
Why would you want to put drive letters into the paths ? BTW, would '../d:/foo' work ? and if not, what's the error message you get ?
Actually, it's not that simple.
The following works, because setup.py lives in d:\bar
../foo
None of these work:
D:/foo /D:/foo //D:/foo D:\foo \D:\foo \D:\foo
Why would you want to put drive letters into the paths ?
Not in this example, but in my real-world scenario the files are on a different drive than setup.py
BTW, would '../d:/foo' work ?
No luck..
and if not, what's the error message you get ?
'File does not exist or is not a regular file'. I think 'd:/foo' gets interpreted as './d:/foo', which is why the file cannot be found.
Peter