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.

Title: Lib/test/ skip testGetServBy if /etc/services is not found
Type: Stage: resolved
Components: Versions:
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: Steap, christian.heimes, iritkatriel, ned.deily, vstinner
Priority: normal Keywords: patch

Created on 2014-03-07 22:57 by Steap, last changed 2022-04-11 14:57 by admin. This issue is now closed.

File name Uploaded Description Edit
skip_testGetServBy.patch Steap, 2014-03-07 22:57 review
Messages (6)
msg212910 - (view) Author: Steap (Steap) Date: 2014-03-07 22:57
In Lib/test/, testGetServBy calls socket.getservbyname(), which needs /etc/services (see "man getservbyname"). If this file is not found, the test fails instead of being skipped.

The attached patch was written against the latest revision of the Mercurial repository. It might be worth applying it for every currently supported version of Python.
msg212912 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2014-03-07 23:20
Unfortunately, how getservbyname() and other similar network interface functions get their data is platform-dependent. /etc/services is a traditional file location but many modern systems use a database or shared database (e.g. NIS) and even allow the system administrator to dynamically change the source of the data.  So, checking for /etc/services would cause the test to be skipped needlessly.  I would think that most systems would not be very usable without a working getservbyname().  Under what circumstances is this causing a problem for you?
msg213016 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-03-10 08:46
I don't understand why /etc/services would miss. What is the current behaviour? What is the error message?
msg213635 - (view) Author: Steap (Steap) Date: 2014-03-15 04:31
I did not know that /etc/services is not always used :/

The main issue is that when you run the test suite in a chroot (to do "pure" builds) or in a network sandbox (for other functions). I get the following errors:

ERROR: testGetServBy (test.test_socket.GeneralModuleTests)
Traceback (most recent call last):
  File "/tmp/nix-build-python-3.3.4.drv-0/Python-3.Lib/test/", line 840, in testGetServBy
    raise socket.error

ERROR: testGetaddrinfo (test.test_socket.GeneralModuleTests)
Traceback (most recent call last):
  File "/tmp/nix-build-python-3.3.4.drv-0/Python-3.Lib/test/", line 1126, in testGetaddrinfo
    socket.getaddrinfo(HOST, "http")
socket.gaierror: [Errno -8] Servname not supported for ai_socktype

ERROR: test_idna (test.test_socket.GeneralModuleTests)
Traceback (most recent call last):
  File "/tmp/nix-build-python-3.3.4.drv-0/Python-3.Lib/test/", line 1186, in test_idna
socket.gaierror: [Errno -2] Name or service not known
msg406598 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2021-11-19 17:05
>  when you run the test suite in a chroot (to do "pure" builds) or in a network sandbox (for other functions)

Do we support that?
msg406599 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2021-11-19 17:10
Nope, we don't have to support this edge case.
Date User Action Args
2022-04-11 14:57:59adminsetgithub: 65067
2021-11-19 17:10:36christian.heimessetstatus: pending -> closed

nosy: + christian.heimes
messages: + msg406599

resolution: rejected
stage: resolved
2021-11-19 17:05:41iritkatrielsetstatus: open -> pending
nosy: + iritkatriel
messages: + msg406598

2014-03-15 04:31:16Steapsetmessages: + msg213635
2014-03-10 08:46:13vstinnersetmessages: + msg213016
2014-03-10 08:45:17vstinnersetnosy: + vstinner
2014-03-07 23:20:42ned.deilysetnosy: + ned.deily
messages: + msg212912
2014-03-07 22:57:22Steapcreate