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

FUJIWARA Katsunori foozy at lares.dti.ne.jp
Thu Aug 9 02:48:16 CDT 2012


Hi, devels.

I found that:

  - platform specific 'realpath()' is defined in posix.py and
    windows.py,

  - 'os.path.realpath' is not replaced by it, so it should be used via
    'util.realpath()', but

  - there is no implementation using 'util.realpath()'

    even though fixing about platform specific 'realpath()' were done
    in 2009, 2010 and 2011:

      - 40196d036a71
      - e98bf6948092
      - ab600a25dfc0

Are there any historical/technical reasons not to use
'util.realpath()' ?

If not, we should use 'util.realpath()' instead of
'os.path.realpath()', shouldn't we ?

I just checked only 'realpath' symbol usage in current implementation,
so please tell me if I overlook any important points.

----------------------------------------------------------------------
[FUJIWARA Katsunori]                             foozy at lares.dti.ne.jp


More information about the Mercurial-devel mailing list