Comment 15 for bug 1445764

I'm not sure why the buildout process is not installing a working python3.4 in mailman-bundler/venv-3.4/, but it isn't. I suggest the following:

1) remove all the symlinks you added. Ones mentioned in the thread starting at <https://mail.python.org/pipermail/mailman-developers/2015-April/024894.html> include:

ln -s /usr/local/bin/python /usr/bin/python
ln -s /usr/local/bin/python3.4 /usr/local/bin/python3
ln -s /usr/local/bin/python3.4 /usr/bin/python3.4

You may not have added all those and you may have added others, but remove all you added.

2) remove the venv and venv-3.4 directories from mailman-bundler/

3) If your mailman-bundler is not at rev. 62, at least do a bzr pull to update it. Better still, remove mailman-bundler/ and start from the beginning.

4) if after running buildout you still don't have a working Python 3 in mailman-bundler/venv3-4, you can probably "fix" it by removing mailman-bundler/venv3-4/lib/python3.4 and replacing it with a symlink to /usr/local/lib/python3.4, but it's not clear to me that the prior symlinking is not somehow involved with the current issue so you should proceed with caution.

The real issue here is why is buildout not installing a complete, working python3.4 in venv-3.4.

What happens if you just do

cd
virtualenv -p python3.4 xxx
./xxx/bin/python