Maksym Shalenyi

@gahjelle thanks for the talk, it was amazing! I think you may be interested in taking a look at [wired](https://wired.readthedocs.io/en/latest/) it kind of similar to `pyplugs` tool.

I've added proposal with alternative solution for referring user's home path https://github.com/buildout/buildout/issues/391

I really would like to not have have any changes in buildout just for making it more compatible with virtualenv and that awful way of assembling envs via "pip install...

@mdeguzis there is recipes that can provide you with functionality that you want, for example with https://pypi.python.org/pypi/gocept.recipe.env/ you can do following: [buildout] parts += ... env develop = ${env:HOME}/path/to/mytool/setup.py [env]...

@jimfulton the downside of approach of replacing `~` with `userpath` everywhere is that it could make managing some special tokens with zc.buildout I way more worse. Adding `"a silent ~...

I've added proposal with alternative solution for referring user's home path https://github.com/buildout/buildout/issues/391

@idgserpro you may be interested in taking a look at `show-picked-versions = true`, it makes buildout to behave somewhat similar to `pip freeze`, especially if you don't have any versions...

@sirex I guess you could make a good use of this two recipes: 1. https://pypi.python.org/pypi/gp.recipe.pip/0.5.3 - runs pip under buildout 2. https://pypi.python.org/pypi/collective.recipe.pip/0.3.2 - extends buildout versions from pip requirements files...

@sirex, sorry for confusion, I was saying it in context of managing packages and dependencies inside project. Venv is great tool for isolation and pip is "an easy" way to...

@sirex , I guess that behaviour can be achieved by combining recipes: - `gp.recipe.pip` will make buildout in charge for version control and assembling with using pip for packages installation...