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 njs
Recipients Thomas.Waldmann, lemburg, njs
Date 2016-07-10.15:14:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468163648.98.0.340719588523.issue26544@psf.upfronthosting.co.za>
In-reply-to
Content
> The purpose of the function was to determine the minimum libc compatibility requirements of the executable.

For what it's worth, I didn't know this, the pip authors obviously didn't know this, and after rereading the docs just now I still can't quite tell that this was intended. I'm not sure why one would want these semantics either, but at a minimum it would help to document the intended semantics much more clearly.

> parsing needs to be kept around as fallback solution

The point of the data I attached was that AFAICT there don't exist any currently-in-use, non-glibc systems where "parsing" returns a meaningful result.
History
Date User Action Args
2016-07-10 15:14:09njssetrecipients: + njs, lemburg, Thomas.Waldmann
2016-07-10 15:14:08njssetmessageid: <1468163648.98.0.340719588523.issue26544@psf.upfronthosting.co.za>
2016-07-10 15:14:08njslinkissue26544 messages
2016-07-10 15:14:08njscreate