[issue29846] ImportError: No module named _io

[Ned Deily]

Ned Deily added the comment:

I'm not familiar with Spack and I'm certainly not going to try to deeply 
analyze a build that inserts *that* many separate -I and -L options into the 
compiler calls :)  But there have been a number of reports of problems with 
this symptom in the past (try searching the web) and at least one previous 
issue opened here (Issue26498).  The root cause in all of these is that at some 
point there is a mismatch between a python executable of one 2.7.x version 
being dynamically linked at run time with python shared libraries of a 
different 2.7.x version.  While a python build should guard against this 
happening, often it doesn't matter when such a mismatch occurs.  However, there 
was an incompatibility introduced in the lifetime of 2.7.x involving 
__PyCodecInfo_GetIncrementalDecoder (I forget the details).  My guess is that 
you will find that the problem goes away if you avoid the use of 
'--enable-shared' on the Python configure; most Python distributions on macOS 
use --enable-framework rathe
 r than --enable-shared and we seldom test it.  Or use neither.  You should 
also check that there are no third-party Python 2.7's on PATH and/or Python 2.7 
shared libraries on the dyld library search paths, other than the 
Apple-supplied pythons in /usr/bin.  It would be nice to finally figure out and 
resolve where the hole is but I've never been able to reproduce the failure 
myself.

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29846] ImportError: No module named _io

[Adam Stewart]

New submission from Adam Stewart:

I'm trying to build Python 2.7.13 with clang on macOS 10.12.3 with the Spack 
package manager, but it fails to build the _io module. The exact error message 
from the build log can be seen here:

https://github.com/LLNL/spack/issues/3478#issuecomment-287548431

This only seems to occur for me on macOS; I can't reproduce it on Linux. I 
checked my environment, but I don't have any Python-related environment 
variables, nor do I have any variables like DYLD_LIBRARY_PATH set that could 
cause problems. I'm a developer for the Spack package manager, so any problems 
that you help me solve will greatly benefit our community.

I have attached the build log. Please let me know if there is any more 
information I can provide you with.

--
components: Build
files: spack-build.out
messages: 289815
nosy: ajstewart
priority: normal
severity: normal
status: open
title: ImportError: No module named _io
type: compile error
versions: Python 2.7
Added file: http://bugs.python.org/file46734/spack-build.out

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com