Reinout van Rees

The PEP 518 made me wonder at the time if that wouldn't be a way forward for buildout: specify buildout as the build-time requirement? Pip would then install buildout and...

I've fixed the main unicode filename problem in #250, though there might be other places.

Buildout 2.4.0 fixes the most immediate unicode problem. I'm leaving the issue open as we might want to do more unicode work.

Setting environment variables would be handy imho. What I do now is to use the "insert python code at the start of the script" option to inject `import os;os.environ['something']='bla bla'`....

Weird. There **is** code that calls `os.path.expanduser()`. https://github.com/buildout/buildout/blob/master/src/zc/buildout/buildout.py#L412 Could it be it sees it as an absolute path? I don't think so, but... https://github.com/buildout/buildout/blob/master/src/zc/buildout/buildout.py#L396

So: it seems OK for buildout (or, I suspect, setuptools) to prefer the "+" variant? Though I must say I also find it a bit strange that an exact version...

Some brainstorming: - We should continue to allow buildout to be initially installed globally or in a virtualenv, as we're starting to prefer that method to `python bootstrap.py` as that...

Is this a change compare to, say, 2.2.0? Can you show us the relevant part of the buildout config (so: the `[buildout]` part)?

Writing to a versions file only happens if you've set the `update-versions-file` option (and filled it with a filename, so `update-versions-file = versions.cfg`, for instance). https://github.com/buildout/buildout/blob/master/src/zc/buildout/buildout.py#L160 The relevant "if" statement...

@papachoco : you probably attached a file to a reply email, but that doesn't show up on github.com :-)