This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients emptysquare, hugh, ionelmc, ronaldoussoren, serhiy.storchaka, terry.reedy, vstinner, yselivanov
Date 2020-05-28.15:37:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590680252.93.0.0862850402947.issue25920@roundup.psfhosted.org>
In-reply-to
Content
If I understood correctly, Python 3.8 and 3.9 binaries provided by python.org is *not* impacted by this issue.

Only Python binaries built manually with explicit support for macOS 10.4 ("MAC_OS_X_VERSION_MIN_REQUIRED") were impacted.

Python 3.9 and older are not fixed (keep the lock). The workaround is to require macOS 10.5 or newer. macOS 10.4 was released in 2004, it's maybe time to stop support it :-)

Python 3.7 (and newer) requires macOS 10.6 or newer (again, I'm talking about binaries provided by python.org).


> bpo-25920: Remove socket.getaddrinfo() lock on macOS (GH-20177)

I chose to leave the lock for gethostbyname(). Ronald wrote that this lock is no longer needed:
"As an aside (not to be addressed in the PR): Apparently gethostbyname() and related functions are thread-safe on macOS. This is according to the manpage on macOS 10.15. I haven't checked in which version that changed. This allows avoiding the use of the gethostbyname lock as well."
https://github.com/python/cpython/pull/20177#pullrequestreview-418909595

Please open a separated issue for this lock.
History
Date User Action Args
2020-05-28 15:37:32vstinnersetrecipients: + vstinner, terry.reedy, ronaldoussoren, ionelmc, serhiy.storchaka, yselivanov, emptysquare, hugh
2020-05-28 15:37:32vstinnersetmessageid: <1590680252.93.0.0862850402947.issue25920@roundup.psfhosted.org>
2020-05-28 15:37:32vstinnerlinkissue25920 messages
2020-05-28 15:37:32vstinnercreate