bpo-41203: Replace OS X with macOS#21316
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
ronaldoussoren
left a comment
There was a problem hiding this comment.
I'm generally in favour of this change, with some reservations:
-
I'd like to keep using "Macintosh" to refer to Mac systems before Darwin (Mac OS 9 and earlier)
-
There are changes to the various NEWS file, I'm not sure if this is a good idea. As far as I know we usually don't edit these.
There's also a number of incorrect changes (see detailed comments).
I haven't reviewed the change to the PDF file.
| 'Intended Audience :: System Administrators', | ||
| 'License :: OSI Approved :: Python Software Foundation License', | ||
| 'Operating System :: MacOS :: MacOS X', | ||
| 'Operating System :: MacOS :: MacmacOS', |
There was a problem hiding this comment.
This one is incorrect for two reasons:
- Spelling error in the new text
- This value is a PyPI classifier, and those still use "MacOS X"
Please revert this change until "macOS" is added as an alternatieve to the PyPI classifiers.
| A manner of interpreting text streams in which all of the following are | ||
| recognized as ending a line: the Unix end-of-line convention ``'\n'``, | ||
| the Windows convention ``'\r\n'``, and the old Macintosh convention | ||
| the Windows convention ``'\r\n'``, and the old Mac convention |
There was a problem hiding this comment.
I'd prefer to keep Macintosh here. This is referring to MacOS 9 and earlier, when Macintosh was commonly used to describe the system.
|
|
||
| Module :mod:`binhex` | ||
| Support for the binhex format used on the Macintosh. | ||
| Support for the binhex format used on the Mac. |
There was a problem hiding this comment.
Same here, I'd prefer to keep Macintosh.
| If you code or decode textfiles on non-Macintosh platforms they will still use | ||
| the old Macintosh newline convention (carriage-return as end of line). | ||
| If you code or decode textfiles on non-Mac platforms they will still use | ||
| the old Mac newline convention (carriage-return as end of line). |
There was a problem hiding this comment.
Likewise (for both lines).
| | | mac_centeuro | | | ||
| +-----------------+--------------------------------+--------------------------------+ | ||
| | mac_roman | macroman, macintosh | Western Europe | | ||
| | mac_roman | macroman, Mac | Western Europe | |
There was a problem hiding this comment.
"macintosh" is the name of an encoding, don't change.
| termination sequences can be used - the Unix form using ASCII LF (linefeed), | ||
| the Windows form using the ASCII sequence CR LF (return followed by linefeed), | ||
| or the old Macintosh form using the ASCII CR (return) character. All of these | ||
| or the old Mac form using the ASCII CR (return) character. All of these |
There was a problem hiding this comment.
I'd prefer to keep the name "Macintosh" here as well.
| Python CE page at http://pythonce.sourceforge.net/ for more information. | ||
|
|
||
| Another new platform is Darwin/MacOS X; initial support for it is in Python 2.0. | ||
| Another new platform is Darwin/MacmacOS; initial support for it is in Python 2.0. |
There was a problem hiding this comment.
Typo, this should be "macOS" instead of "MacmacOS".
| Recent versions of the GUSI development environment for MacOS support POSIX | ||
| threads. Therefore, Python's POSIX threading support now works on the | ||
| Macintosh. Threading support using the user-space GNU ``pth`` library was also | ||
| Mac. Threading support using the user-space GNU ``pth`` library was also |
| to Fredrik Lundh. | ||
|
|
||
| * Some new ports were contributed: MacOS X (by Steven Majewski), Cygwin (by | ||
| * Some new ports were contributed: MacmacOS (by Steven Majewski), Cygwin (by |
|
|
||
| * The code for the MacOS port for Python, maintained by Jack Jansen, is now kept | ||
| in the main Python CVS tree, and many changes have been made to support MacOS X. | ||
| in the main Python CVS tree, and many changes have been made to support MacmacOS. |
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
RE changes to the NEWS files, I totally agree (especially the older ones) - it looks a bit anachronistic to have macOS references in the same breath as talking about Mac OS 9 and Macintosh. That's why I did them in separate commits, so it would be easier to cherrypick/rebase/whatever if they weren't wanted. Should I completely reset them? |
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @ronaldoussoren: please review the changes made to this pull request. |
serhiy-storchaka
left a comment
There was a problem hiding this comment.
Do not use anachronical macOS for versions which predated the name macOS.
|
|
||
| This module encodes and decodes files in binhex4 format, a format allowing | ||
| representation of Macintosh files in ASCII. Only the data fork is handled. | ||
| representation of Mac files in ASCII. Only the data fork is handled. |
| :noindex: | ||
|
|
||
| The default mode which is used to load shared libraries. On OSX 10.3, this is | ||
| The default mode which is used to load shared libraries. On macOS 10.3, this is |
There was a problem hiding this comment.
It was Mac OS X for versions up to 10.7 inclusively.
| .. note:: | ||
|
|
||
| On Mac OS X, :func:`getgroups` behavior differs somewhat from | ||
| On macOS, :func:`getgroups` behavior differs somewhat from |
There was a problem hiding this comment.
I have doubts about this one. If the note refers to 10.5 and earlier, it should be Mac OS X.
| .. availability:: Unix. | ||
|
|
||
| .. note:: On Mac OS X, the length of *groups* may not exceed the | ||
| .. note:: On macOS, the length of *groups* may not exceed the |
|
|
||
| On POSIX platforms, this means that file owner and group are lost as well | ||
| as ACLs. On Mac OS, the resource fork and other metadata are not used. | ||
| as ACLs. On macOS, the resource fork and other metadata are not used. |
There was a problem hiding this comment.
Is it relevant to modern macOS or only to classic MacOS?
| ================================ | ||
|
|
||
| Mac OS X 10.8 comes with Python 2.7 pre-installed by Apple. If you wish, you | ||
| macOS 10.8 comes with Python 2.7 pre-installed by Apple. If you wish, you |
There was a problem hiding this comment.
Current versions of macOS still have Python 2.7 I believe
| Mac OS X. Packages and documentation are available from https://www.wxpython.org. | ||
| macOS. Packages and documentation are available from https://www.wxpython.org. | ||
|
|
||
| *PyQt* is another popular cross-platform GUI toolkit that runs natively on Mac |
There was a problem hiding this comment.
"Mac macOS" -> "macOS"
| enabled by supplying the :option:`!--enable-framework` option to the configure | ||
| script when compiling Python. According to Jack Jansen, "This installs a | ||
| self-contained Python installation plus the OS X framework "glue" into | ||
| self-contained Python installation plus the macOS framework "glue" into |
| The main change is the possibility to build Python as a | ||
| framework. This installs a self-contained Python installation plus the | ||
| OSX framework "glue" into /Library/Frameworks/Python.framework (or | ||
| macOS framework "glue" into /Library/Frameworks/Python.framework (or |
|
|
||
| The three major operating systems used today are Microsoft Windows, Apple's | ||
| Macintosh OS, and the various Unix derivatives. A minor irritation of | ||
| Mac OS, and the various Unix derivatives. A minor irritation of |
serhiy-storchaka
left a comment
There was a problem hiding this comment.
There are incorrect changes. My comments have not yet been addressed.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase And if you don't make the requested changes, you will be put in the comfy chair! |
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @ronaldoussoren, @serhiy-storchaka: please review the changes made to this pull request. |
|
|
||
| Mac OS Platform | ||
| macOS Platform | ||
| --------------- |
There was a problem hiding this comment.
The length of the underlying line should be corrected.
| are skipped. For the tail part, it uses the empty string and then | ||
| :file:`lib/site-packages` (on Windows) or | ||
| :file:`lib/python{X.Y}/site-packages` (on Unix and Macintosh). For each | ||
| :file:`lib/python{X.Y}/site-packages` (on Unix and Mac). For each |
| :func:`getuserbase` hasn't been called yet. Default value is | ||
| :file:`~/.local` for UNIX and Mac OS X non-framework builds, | ||
| :file:`~/.local` for UNIX and macOS non-framework builds, | ||
| :file:`~/Library/Python/{X.Y}` for Mac framework builds, and |
| in a case insensitive approach, for all operating systems first, and when it | ||
| cannot find it, looks for proxy information from Mac OSX System | ||
| Configuration for Mac OS X and Windows Systems Registry for Windows. | ||
| cannot find it, looks for proxy information from macOS System |
There was a problem hiding this comment.
On Apple's site it is called just "System Configuration".
| Internet Settings section, and in a Mac OS X environment proxy information | ||
| is retrieved from the OS X System Configuration Framework. | ||
| Internet Settings section, and in a macOS environment proxy information | ||
| is retrieved from the macOS System Configuration Framework. |
There was a problem hiding this comment.
I think it is just "the System Configuration framework".
|
|
||
| *************************** | ||
| Using Python on a Macintosh | ||
| Using Python on a Mac |
There was a problem hiding this comment.
The number of *s should match the length of the title.
|
|
||
| *************************** | ||
| Using Python on a Macintosh | ||
| Using Python on a Mac |
There was a problem hiding this comment.
According to Wikipedia "Mac" is a correct name for modern Apple's computers.
| Mac OS X. Packages and documentation are available from https://www.wxpython.org. | ||
| macOS. Packages and documentation are available from https://www.wxpython.org. | ||
|
|
||
| *PyQt* is another popular cross-platform GUI toolkit that runs natively on Mac |
There was a problem hiding this comment.
"Mac macOS" -> "macOS"
I've made separate commits for changes in old whatsnew files because maybe they should be kept as is, for historical reasons?
Also I've committed changes from "Macintosh" to "Mac".
All of these changes were made with
sedso I can't guarantee there are no false-positives, although I tried...https://bugs.python.org/issue41203