Oh yeah sorry, the path to python3.4 was hardcoded. I fixed this an hour ago, sorry for not replying earlier but I was on a plane from PyCon. Please update your mailman-bundler branch.

Hi Aurélien Bompard!

Thank you for patching. Now this error does not occur.

But I stil can't build the mailman with the error I reposted in the bottom of my bug report:

--- (venv)[root@host mailman-bundler]# buildout Develop: '/usr/local/src/mailman-bundler/.' warning: no files found matching '*.in' under directory 'mailman_bundler' warning: no files found matching '*.in' under directory 'deployment' warning: no files found matching 'deployment/mailman-web.logrotate.conf' Updating mailman-web. Updating main. Installing mailman. Running virtualenv with interpreter /usr/local/bin/python3.4 Using base prefix '/usr/local' New python executable in /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 Not overwriting existing python script /usr/local/src/mailman-bundler/venv-3.4/bin/python (you must use /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4) Failed to import the site module Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site.py", line 67, in <module> import os File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/os.py", line 616, in <module> from _collections_abc import MutableMapping ImportError: No module named '_collections_abc' ERROR: The executable /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 is not functioning ERROR: It thinks sys.prefix is '/usr/local/src/mailman-bundler' (should be '/usr/local/src/mailman-bundler/venv-3.4') ERROR: virtualenv is not compatible with this system or executable /tmp/tmpeMECwh/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: Нет такого файла или каталога While: Installing mailman.

An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1946, in main getattr(buildout, command)(args) File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 626, in install installed_files = self[part]._call(recipe.install) File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1370, in _call return f() File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install self.execute() File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute run_commands(cmds, self.shell) File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands check_call('%s %s' % (shell, tmpfile), shell=True) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'sh /tmp/tmpeMECwh/run' returned non-zero exit status 127

---

Should I fill another bug report for this case?

Everything worked for me on Ubuntu 15.04

Aurélien:

Could you be missing some devel libraries?

I don't think so but I'm ready to check something yo want.

Does your distribution have a version of Python 3.4 that would be

parallel-installable?

I could not find any with "yum search python". As I reported, this is fresh new Centos 7 installation.

Mark:

I did everything you advice with the error posted above.

Few more experiments:

(venv)[root@host mailman-bundler]# ls -l /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 -rwxr-xr-x 1 root root 17544 apr 18 22:55 /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4

(venv)[root@host mailman-bundler]# /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 Failed to import the site module Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site.py", line 67, in <module> import os File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/os.py", line 616, in <module> from _collections_abc import MutableMapping ImportError: No module named '_collections_abc'

I have very poor knowing of Python and its environment. I'm unable to find what's wrong with the Python installation.

I can provide to you any additional data if you request.

There is something wrong with your Python 3.4.

What happens if you just do

$ /usr/local/bin/python3.4

...

...

import os import _collections_abc

and

$ /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4

...

...

import os import _collections_abc

I suspect you will get ImportError on all of those which means your Python 3.4 install is broken. You need to have a working Python 3.4 that can successfully

import os

/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4 is a directory!

Sorry, that should have been

/usr/local/src/mailman-bundler/venv-3.4/bin/python3.4

but the fact that I don't see _collections_abc.py in the lib directory could be an issue unless it's in site-packages.

Here's what mine looks like.

$ ls -F mailman-bundler/venv-3.4/lib/python3.4 abc.py@ hmac.py@ rlcompleter.py@ base64.py@ importlib@ shutil.py@ bisect.py@ imp.py@ site-packages/ _bootlocale.py@ io.py@ site.py codecs.py@ keyword.py@ sre_compile.py@ collections@ lib-dynload@ sre_constants.py@ _collections_abc.py@ linecache.py@ sre_parse.py@ config-3.4m-x86_64-linux-gnu@ locale.py@ stat.py@ copy.py@ no-global-site-packages.txt struct.py@ copyreg.py@ ntpath.py@ tarfile.py@ distutils/ operator.py@ tempfile.py@ _dummy_thread.py@ orig-prefix.txt tokenize.py@ encodings@ os.py@ token.py@ fnmatch.py@ plat-x86_64-linux-gnu@ types.py@ functools.py@ posixpath.py@ warnings.py@ __future__.py@ __pycache__/ weakref.py@ genericpath.py@ random.py@ _weakrefset.py@ hashlib.py@ reprlib.py@ heapq.py@ re.py@

The ones with '@' are all symlinks to the corresponding /usr/lib/python3.4/ file.

I have reinstalled Python 3.4.3, checked if everything is all right with its installation.

I can see '_collections_abc.py' module in /usr/local/lib/python3.4 directory.

But there is no such file in

(venv)[root@host mailman-bundler]# ls -F venv-3.4/lib/python3.4 abc.py@ copy.py@ __future__.py@ lib-dynload@ orig-prefix.txt reprlib.py@ sre_compile.py@ tarfile.py@ warnings.py@ bisect.py@ copyreg.py@ genericpath.py@ linecache.py@ os.py@ re.py@ sre_constants.py@ tempfile.py@ weakref.py@ codecs.py@ encodings@ heapq.py@ locale.py@ posixpath.py@ shutil.py@ sre_parse.py@ tokenize.py@ _weakrefset.py@ collections@ fnmatch.py@ io.py@ no-global-site-packages.txt __pycache__/ site-packages/ stat.py@ token.py@ config-3.4m@ functools.py@ keyword.py@ ntpath.py@ random.py@ site.py struct.py@ types.py@

So, I think that the problem is somewhere in the process of 'venv-3.4' directory creation.

1) All they were removed right after they did not help.

2) Removed several times with the whole mailman-bundler/ directory.

3) Did it all the time after pulling once.

4) I don't want to fix or work around, I can wait until we will understand what happening. I 'm going to run additional tests with another version of Centos tomorrow.

Answer:

[root@host ~]# cd [root@host ~]# virtualenv -p python3.4 xxx Running virtualenv with interpreter /usr/local/bin/python3.4 Using base prefix '/usr/local' New python executable in xxx/bin/python3.4 Also creating executable in xxx/bin/python Failed to import the site module Traceback (most recent call last): File "/root/xxx/lib/python3.4/site.py", line 67, in <module> import os File "/root/xxx/lib/python3.4/os.py", line 616, in <module> from _collections_abc import MutableMapping ImportError: No module named '_collections_abc' ERROR: The executable xxx/bin/python3.4 is not functioning ERROR: It thinks sys.prefix is '/root' (should be '/root/xxx') ERROR: virtualenv is not compatible with this system or executable [root@host ~]# ./xxx/bin/python Failed to import the site module Traceback (most recent call last): File "/root/xxx/lib/python3.4/site.py", line 67, in <module> import os File "/root/xxx/lib/python3.4/os.py", line 616, in <module> from _collections_abc import MutableMapping ImportError: No module named '_collections_abc'

It is 1.10.1 version here on Centos 7.

I have installed setuptools 15.1 but it can't help me to install 'virtualenv' newer than 1.10.1:

[root@host ~]# easy_install virtualenv # note that correct spelling easy_install, not easy-install! Searching for virtualenv Best match: virtualenv 1.10.1 Adding virtualenv 1.10.1 to easy-install.pth file

Using /usr/lib/python2.7/site-packages Processing dependencies for virtualenv Finished processing dependencies for virtualenv

---

Did I miss something, Mark?

Hi, I am just installing Mailman on CentOs 7 and already installed Python 3.5 and get the exact same output after typing buildout:

Installing mailman. The executable python3.4 (from --python=python3.4) does not exist /tmp/tmptaILCi/run: line 2: /root/mailman-bundler/venv-3.4/bin/pip: No such file or directory While: Installing mailman.

An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1992, in main getattr(buildout, command)(args) File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 666, in install installed_files = self[part]._call(recipe.install) File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1407, in _call return f() File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install self.execute() File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute run_commands(cmds, self.shell) File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands check_call('%s %s' % (shell, tmpfile), shell=True) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'sh /tmp/tmptaILCi/run' returned non-zero exit status 127

What to do now?