Hi All, I'm not sure there's anything you can do about this, but I thought I should alert the Python devs that it can happen...
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? -- Dave Abrahams BoostPro Computing http://www.boostpro.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
