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 lemburg
Recipients Thomas.Waldmann, lemburg, njs
Date 2016-07-10.10:37:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
At the time the code was written, libc and glibc were in wide spread use, so it's not surprising that it doesn't work well for other C libs.

Note that the routine returns the highest libc version number used and required by the executable (usually the Python interpreter). This does not necessarily correspond to the version installed on the system. The purpose of the function was to determine the minimum libc compatibility requirements of the executable.

The routine you quote uses ctypes and only works for glibc, so parsing needs to be kept around as fallback solution. It also returns the libc version that is currently used on the system; not necessarily the minimum version required, so semantics are different.
Date User Action Args
2016-07-10 10:37:00lemburgsetrecipients: + lemburg, njs, Thomas.Waldmann
2016-07-10 10:37:00lemburgsetmessageid: <>
2016-07-10 10:37:00lemburglinkissue26544 messages
2016-07-10 10:37:00lemburgcreate