i compiled and installed the release version of python 2.5 for linux to
a directory accessible to 2 computers, configured with
--prefix=/usr/arch (which is accessible to both machines). the
installation went fine and when i run python on one machine i can do
from hashlib import * without a
samn wrote:
i compiled and installed the release version of python 2.5 for linux to
a directory accessible to 2 computers, configured with
--prefix=/usr/arch (which is accessible to both machines). the
installation went fine and when i run python on one machine i can do
from hashlib import *
I believe the _md5 module (as opposed to the md5 module) is a compiled
extension. I'm guessing the import succeeds on the machine you used to
build python.
Try
import _md5
print _md5.__file__
and see if you can find out where it's being loaded from. You'll
probably find that you
samn wrote:
I believe the _md5 module (as opposed to the md5 module) is a compiled
extension. I'm guessing the import succeeds on the machine you used to
build python.
Try
import _md5
print _md5.__file__
and see if you can find out where it's being loaded from. You'll
probably find that
i think the problem is different versions of openssl on the two
machines , 0.9.7a and 0.9.8b
--
http://mail.python.org/mailman/listinfo/python-list
On Mon, Oct 23, 2006 at 01:28:46PM -0700, samn wrote:
i think the problem is different versions of openssl on the two
machines , 0.9.7a and 0.9.8b
I second that this is the likely culprit. I got bit by it while trying to
do cross compile. The module build process assumes a couple of locations
Chris Lambacher wrote:
On Mon, Oct 23, 2006 at 01:28:46PM -0700, samn wrote:
i think the problem is different versions of openssl on the two
machines , 0.9.7a and 0.9.8b
I second that this is the likely culprit. I got bit by it while trying to
do cross compile. The module build process
