、os.path
が実際にある:
ntpath.py
のWindows
posixpath.py
のためのLinux
macpath.py
は、Mac OSX用
os
モジュールは、これはで言いますファイルの先頭:
r"""OS routines for NT or Posix depending on what system we're on.
This exports:
- all functions from posix, nt, os2, or ce, e.g. unlink, stat, etc.
- os.path is one of the modules posixpath, or ntpath
- os.name is 'posix', 'nt', 'os2', 'ce' or 'riscos'
- os.curdir is a string representing the current directory ('.' or ':')
- os.pardir is a string representing the parent directory ('..' or '::')
- os.sep is the (or a most common) pathname separator ('/' or ':' or '\\')
- os.extsep is the extension separator ('.' or '/')
- os.altsep is the alternate pathname separator (None or '/')
- os.pathsep is the component separator used in $PATH etc
- os.linesep is the line separator in text files ('\r' or '\n' or '\r\n')
- os.defpath is the default search path for executables
- os.devnull is the file path of the null device ('/dev/null', etc.)
Programs that import and use 'os' stand a better chance of being
portable between different platforms. Of course, they must then
only use functions that are defined by all platforms (e.g., unlink
and opendir), and leave all pathname manipulation to os.path
(e.g., split and join).
"""
macのための 'macpath.py' –
私はちょうど確認したPythonのすべてのバージョンのdocstringからその文字列を残したようです...そのためのcpythonリポジトリへのPRを入れるかもしれないと思います。 –
OK、ありがとう、私はとてもばかだ。 この回答には理由があります。 [リンク](http://stackoverflow.com/questions/2724348/should-i-use-import-os-path-or-import-os) –