Closed mayeut closed 4 years ago
Replacing https://github.com/pypa/virtualenv/blob/43ccf4a14bb74b0119b49d025d200d927151e229/virtualenv.py#L1623
By :
if '-32' in os.path.basename(py_executable):
try:
call_subprocess(["lipo", original_python, "-thin", "i386", "-output", py_executable])
except Exception:
logger.fatal("Could not call lipo -- you must " "have Apple's development tools installed")
raise
else:
shutil.copy(original_python, py_executable)
after macOS framework detection seems to do the trick.
The trick does not seem to work for python2.
I don't think this is an issue anymore, and if so please check if with the rewrite branch it still is.
Still an issue on master branch, not on rewrite branch.
Then will be fixed once the rewrite lands.
pip list
output Running on macOS 10.14.6, official python.org installer of python 3.7.5 (macOS 64-bit/32-bit installer)python3.7-32 - m pip list
The
venv
module works on 3.7 but does not exist on python 2.7 and so, is not an option at the momentOne difference I can see between the 2 modules is that
venv
creates symlinks whilevirtualenv
creates a copy. The copy seems to be from the dual-architecture python instead of the singlei386
python.