More update on this patch: It's incomplete, and possibly wrong, unfortunately. The issue that someone else noticed is that it does not handle the case when Python was configured with --libdir=...; and I think that the default lib dir on platforms such as Windows and Darwin might be different from the traditional <prefix>/lib as well, although I don't remember anymore (I did the investigation a couple of weeks ago).

I tried to find simple ways to update the script to make it work with a different libdir, but to no avail. :-(

I think that the best option is to enhance the sysconfig module to return the relocated lib path, but the problem is that the script would no longer work with older versions of Python (as older versions of Python would be missing that function). Perhaps one possible acceptable compromise is to call that function only when available and default to the old behavior otherwise. So it'd still be working as well as it does now with older versions of Python, while being slightly better with newer ones...

Just some thoughts...