[issue957650] Fix for bugs relating to ntpath.expanduser()

Geoffrey Bache added the comment: In fact, wouldn't a very simple fix be to not return paths that don't exist? That would probably catch 90% of the cases. -- ___ Python tracker ___

[issue957650] Fix for bugs relating to ntpath.expanduser()

Geoffrey Bache added the comment: Just ran into this myself, and would agree with Christian's comments. On my system, my home directory is a mounted network drive, hence "H:\". It was a bit of a surprise when os.path.expanduser("~fred") returned "H:\\fred"... This seems broken to me. It's surel

[issue957650] Fix for bugs relating to ntpath.expanduser()

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- assignee: loewis -> priority: high -> normal resolution: -> accepted status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> __

[issue957650] Fix for bugs relating to ntpath.expanduser()

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Martin, do you concur? Not really. On my system, which is part of a domain, expanduser("~") gives 'C:\\Documents and Settings\\martin.vonloewis', which is indeed the directory where my profile lives. HOMEDRIVE is Y:, and HOMESHARE is some

[issue957650] Fix for bugs relating to ntpath.expanduser()

Christian Heimes <[EMAIL PROTECTED]> added the comment: I just saw this bug entry in the whatsnew list. The os.path.expanduser() function handles ~user the wrong way. The (naive) implementation expects that all user directories are inside a common base path. This is only true for standalone Windo