Kamal Mustafa

I made initial commit to play around with fixing this. If the changes look fine, I'll clean it up and submit a PR.

For the past few years, this is how our `bootstrap.py` look like:- ``` python import os import sys import subprocess import functools run = functools.partial(subprocess.call, shell=True) run('virtualenv -p python3 .env')...

This is example of using shell script that I've been toying around before settling up for python snippet above:- ``` #!/bin/bash # alternative to http://downloads.buildout.org/2/bootstrap.py (assuming you already have pip...

@leorochael I don't understand yet how the patch work (you don't add .ovo to the path scan) but it seem to work ! Is this viable for permanent fix in...

Aah, I see. I'm currently looking at https://github.com/buildout/buildout/blob/master/src/zc/buildout/tests.py, finding a way to write test for this. Then I'll submit a proper PR.

The only comment added for the [commit](https://github.com/buildout/buildout/commit/8d06c3c3f371020f96596a4fc3878cf05be65d1b):- > pyc and pyo files are regenerated for installed eggs so that the > stored path in code objects matches the the install...

Initially got this error too:- ``` venv/bin/pip freeze --all pip==9.0.1 setuptools==30.2.0 virtualenv==15.0.3 zc.buildout==2.9.3 ``` Created the venv with `python3 -mvenv venv`, using python-3.6.1. But after running `venv/bin/pip install -U setuptools`,...

Never run into this. We also use pip to install buildout. This is our bootstrap.py:- ```python import os import sys import subprocess import functools run = functools.partial(subprocess.call, shell=True) run('virtualenv -p...

Seem to work so far. This PR prevent me from going away ;)

It took me few minutes to realize this, --werkzeug option should be to enable it, not disable. Otherwise it should be --nowerkzeug so it consistent with other command options such...