Ronald Oussoren added the comment:
I'm closing this issue because a patch simular to the attached patch was
applied in r78835 and the issue therefore fixed.
--
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
___
Pyth
Marc-Andre Lemburg added the comment:
Looking at the code, the whole approach to finding the project base appears to
be very fragile.
I'd suggest to use a landmark file for finding the project base, say
"Modules/main.c", and a function which searches all directories on the
os.path.realpath(s
Ronald Oussoren added the comment:
I'd expect more failures, the failure is caused by the way the sysconfig module
calculates the root of the installation, and whether or not it is running in
the source tree.
Tarek: could you please review sysconfig.patch?
--
___
Meador Inge added the comment:
I am seeing the same problem with 32-bit on OS X 10.5:
euclid:trunk minge$ ./python.exe Lib/test/regrtest.py -uall test_platform
test_platform
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "", line 1, in
File "/Users/minge
Ronald Oussoren added the comment:
This test seems to trigger an issue in site.py, adding '-v' to the code that
starts the interpreter in test_platform.py gives the following output (amongst
a lot more text that doesn't seem to be relevant):
'import site' failed; traceback:
Traceback (most re
New submission from Mark Dickinson :
With a 64-bit debug non-framework builds of the trunk and py3k, on OS X 10.6,
I'm consistently getting the following failure in test_platform:
trunk dickinsm$ ./python.exe Lib/test/regrtest.py -uall test_platform
test_platform
[18064 refs]
'import site' fail
