Why is not platform specific 'realpath' used instead of 'os.path.realpath' ?

[Pierre-Yves David]

On 9 août 2012, at 12:30, Mads Kiilerich wrote:
> Some digging shows that it was used in http://selenic.com/repo/hg/rev/26fa0e31011d but backed out again in http://selenic.com/repo/hg/rev/f6683a7011e9 .
> 
> It was discussed around http://www.selenic.com/pipermail/mercurial-devel/2011-October/ . It was fixed http://selenic.com/repo/hg/rev/ab600a25dfc0 and used http://selenic.com/repo/hg/rev/42630f54e513 and used everywhere http://selenic.com/repo/hg/rev/dbdb777502dc ... and all uses backed out again in http://selenic.com/repo/hg/rev/c519cd8f0169 .
> 
> Here be dragons!
> 
> But yes, all uses of os.path should IMO go away and be replaced by the VFS (or other means).

This sound like something that need a check-code.py rule.

-- 
Pierre-Yves