Be warned that pyenv has a nasty bug: <https://git...
# development
h
Be warned that pyenv has a nasty bug: https://github.com/pantsbuild/pex/issues/2021.
f
I've seen similar issue before with a shared libpython
.so
and incorrect rpath or no rpath. You end up getting a python executable dynamically linked at runtime against the wrong
libpython.so
, then boom.
so the error here is either (1) no rpath flag was specified any more and so the 2.7.16 libpython.so was picked up from the default shared libraries path; or (2) the rpath flag was set but with the 2.7.16 libpython.so.
educated guess based on the commit you bisected to being the code setting the rpath
e
I had definitely danced in this arena before: https://github.com/pantsbuild/pex/blob/f326835f068088fd9f75929cadf02006f10dfa32/pex/testing.py#L504-L513 Maybe that could be rethought given newer pyenv setup.