Comment 1 for bug 1388477

Yes it looks as if the anybox.paster.odoo that's in the virtualenv stealed the namespace, and I don't know if that can be solved easily (not the first time I hear about this, I think).

On the other hand, it's always been said (and I hope stated very clearly in the documentation) that the virtualenvs in which the buildout will be bootstrapped/run must be completeley empty (not even setuptools/pip). I agree this might look heavy-handed, but on the other hand you can reuse such a virtualenv for all your buildouts.

If that's not clear enough in the documentation, then please update the documentation.
If you have are willing to spend the hours finding a fix for this, that can be validated with different situations, of course I'll welcome it and update the guidelines -- but it should then work for a lot of setups, and that's opening a can of worms, I fear it'll be more complicated in the end