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