[issue26406] getaddrinfo is thread-safe on NetBSD and OpenBSD

2016-02-23 Thread A. Jesse Jiryu Davis
A. Jesse Jiryu Davis added the comment: Thank you! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue26406] getaddrinfo is thread-safe on NetBSD and OpenBSD

2016-02-23 Thread Ned Deily
Ned Deily added the comment: Thanks for the additional patch, Jesse. Since we don't have a NetBSD buildbot and I don't have any NetBSD or OpenBSD systems at hand to do any testing, I'll take your word for the version checks. If anyone runs into any problems because of these changes, feel free

[issue26406] getaddrinfo is thread-safe on NetBSD and OpenBSD

2016-02-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset 52a8c1965750 by Ned Deily in branch '2.7': Issue #26406: Avoid unnecessary serialization of getaddrinfo(3) calls on https://hg.python.org/cpython/rev/52a8c1965750 New changeset 419d20551d26 by Ned Deily in branch '3.5': Issue #26406: Avoid unnecessa

[issue26406] getaddrinfo is thread-safe on NetBSD and OpenBSD

2016-02-21 Thread A. Jesse Jiryu Davis
A. Jesse Jiryu Davis added the comment: Patch uploaded. I've copied the "nosy" list from #25924, if that was bad etiquette please forgive me. -- keywords: +patch Added file: http://bugs.python.org/file41998/26406-getaddrinfo-netbsd-openbsd.patch __

[issue26406] getaddrinfo is thread-safe on NetBSD and OpenBSD

2016-02-21 Thread A. Jesse Jiryu Davis
New submission from A. Jesse Jiryu Davis: In socketmodule.c we lock around getaddrinfo calls on platforms where getaddrinfo is believed not to be thread-safe. We've verified that it *is* thread-safe, and therefore stopped locking around it, on FreeBSD 5.3+ (#1288833) and Mac OS X 10.5+ (#25924