First of all, this is great, and I'm hugely in favour of something like this going forward. Great work! ...however, I strongly disagree on the benefit of makin

First of all, this is great, and I'm hugely in favour of something like this going forward. Great work! ...however, I strongly disagree on the benefit of making the `Pipfile` executable python. Just read this gist: https://gist.github.com/kennethreitz/4745d35e57108f5b766b8f6ff396de85 https://gist.github.com/kennethreitz/4745d35e57108f5b766b8f6... - This file will be "compiled" down to json. Then why does it exist? We know it'll be abused; and we should have learnt our lesson from scons and setup.py that it wasn't a great idea before, and still isn't a great idea using python code itself as a declarative DSL. Just use a standard hierarchical file format (json, toml, xml, whatever) Features of introspecting and editing `Pipfile.lock` should be rolled into pip and exported as a core python module; an api for editing pipfile.lock is a good idea, but executing a `Pipefile`, is not.