[Python-Dev] Possibility of binary configuration mismatch

[Paul Moore]

2009/5/29 David Abrahams <dave at boostpro.com>:
> http://allmydata.org/trac/tahoe/ticket/704#comment:7 describes a
> situation where my macports-installed python25 had a pyOpenSSL egg
> installed in it by something other than macports (possibly by
> easy_install-2.5?) that was not compatible with the Python build.  My
> hunch is that the pyOpenSSL had binaries compiled against a UCS4 Python,
> but I don't know for sure.  Whatever did the installation of the bad egg
> was almost certainly being executed by the macports python25 because
> macports is installed in /opt/local, and nothing is likely to have
> installed it under that prefix by chance.  In other words, this egg
> probably couldn't have been left over from some non-macports python
> installation.  In fact, I haven't had any other version of Python2.5
> installed on this machine.  Very odd.
>
> I wonder if it makes sense to enhance the extension module system to
> record this kind of information so the problem can be diagnosed by the
> system?

I have a feeling that this has been discussed before, in the context
of easy_install/setuptools' approach to encoding the build details for
a binary package in the filename, not covering UCS4 vs UCS2. You may
find it useful to search on the distutils-sig archives for further
information.

Paul.