mirror of
https://github.com/python/cpython.git
synced 2025-08-04 00:48:58 +00:00
Merged revisions 66452 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk ........ r66452 | georg.brandl | 2008-09-13 19:41:16 +0200 (Sat, 13 Sep 2008) | 2 lines Remove things specific to the old Macintosh, and spell "Mac OS X" consistently. ........
This commit is contained in:
parent
a6fc212d2a
commit
c575c90647
28 changed files with 161 additions and 176 deletions
|
@ -326,7 +326,7 @@ This module provides the following functions.
|
|||
``'posix'``, ``'nt'``), and *compiler* defaults to the default compiler for
|
||||
that platform. Currently only ``'posix'`` and ``'nt'`` are supported, and the
|
||||
default compilers are "traditional Unix interface" (:class:`UnixCCompiler`
|
||||
class) and Visual C++(:class:`MSVCCompiler` class). Note that it's perfectly
|
||||
class) and Visual C++ (:class:`MSVCCompiler` class). Note that it's perfectly
|
||||
possible to ask for a Unix compiler object under Windows, and a Microsoft
|
||||
compiler object under Unix---if you supply a value for *compiler*, *plat* is
|
||||
ignored.
|
||||
|
|
|
@ -302,8 +302,8 @@ or the :command:`bdist` command with the :option:`--formats` option::
|
|||
|
||||
If you have a pure module distribution (only containing pure Python modules and
|
||||
packages), the resulting installer will be version independent and have a name
|
||||
like :file:`foo-1.0.win32.exe`. These installers can even be created on Unix or
|
||||
Mac OS platforms.
|
||||
like :file:`foo-1.0.win32.exe`. These installers can even be created on Unix
|
||||
platforms or Mac OS X.
|
||||
|
||||
If you have a non-pure distribution, the extensions can only be created on a
|
||||
Windows platform, and will be Python version dependent. The installer filename
|
||||
|
|
|
@ -88,7 +88,7 @@ regular filename characters, ``?`` matches any single regular filename
|
|||
character, and ``[range]`` matches any of the characters in *range* (e.g.,
|
||||
``a-z``, ``a-zA-Z``, ``a-f0-9_.``). The definition of "regular filename
|
||||
character" is platform-specific: on Unix it is anything except slash; on Windows
|
||||
anything except backslash or colon; on Mac OS 9 anything except colon.
|
||||
anything except backslash or colon.
|
||||
|
||||
**\*\*** Windows support not there yet **\*\***
|
||||
|
||||
|
|
|
@ -46,9 +46,7 @@ Distutils will take care of converting this platform-neutral representation into
|
|||
whatever is appropriate on your current platform before actually using the
|
||||
pathname. This makes your setup script portable across operating systems, which
|
||||
of course is one of the major goals of the Distutils. In this spirit, all
|
||||
pathnames in this document are slash-separated. (Mac OS 9 programmers should
|
||||
keep in mind that the *absence* of a leading slash indicates a relative path,
|
||||
the opposite of the Mac OS convention with colons.)
|
||||
pathnames in this document are slash-separated.
|
||||
|
||||
This, of course, only applies to pathnames given to Distutils functions. If
|
||||
you, for example, use standard Python functions such as :func:`glob.glob` or
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue