Could you please revisit the Python-2.x-and-Python-3.x workflow with MacVim

Hi,
This is a great reference and it seems like many people used it in the past:
Python-2.x-and-Python-3.x

However, I would say, the solution suggested at the link above is failing with multiple different issues.

Could you (anyone with experience) please update that solution, and maybe in that way we can make sure that this works with the latest Python2.x and Python3.x versions and pyenv, conda etc.

For example, in my case the pyenv installation for Python2.x and Python3.x described in that link was extreemly painful.

Then the homebrew bit did not work.

I also was not sure if the dynamic linking was working at all. My otool -L output is:

otool -L _ctypes.so
_ctypes.so:
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4)

And I never managed to get this bit to work:

$ otool -L $HOME/.pyenv/versions/2.7.11/lib/python2.7/lib-dynload/_ctypes.so
/Users/foo/.pyenv/versions/2.7.11/lib/python2.7/lib-dynload/_ctypes.so:
    /Users/foo/.pyenv/versions/2.7.11/lib/libpython2.7.dylib (compatibility version 2.7.0, current version 2.7.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

Many plugins are now using Python3 and some are still using Python2. A hybrid solutions is becoming critical even more now.

Thank you very much.

Start with the Python-2.x-and-Python-3.x MacVim wiki page and reproduce the reported pyenv, Homebrew, and dynamic-linking problems using the commands and otool output in the issue. Done means the page documents a working hybrid setup for Python 2 and Python 3, including current pyenv or conda guidance and verified dynamic linking.