[20:02:43] <aclark> kennethreitz: for this… you will pay… a terrible price ;-) Seriously though, see my tools rant: http://pythonpackages-docs.readthedocs.org/en/latest/build.html#buildout-easy-install-vs-virtualenv-pip You guys should support it, or at least consider the logistics
[20:03:14] <aclark> kennethreitz: it does not mutually exclude pip, it's on top of pip (more or less)
[20:19:25] <kennethreitz> aclark: what can you not accomplish with pip?
[20:30:18] <aclark> kennethreitz: buildout supports ini-style config with pluggable recipes, so there is a huge ecosystem there to support (not that heroku necessarily wants to be in that biz). for a concrete answer look at plone, not sure how many folks will be able to handle this method: http://pythonpackages.com/info/isotoma.plone.heroku
[20:30:54] <aclark> kennethreitz: if you supported it i think you'd see a lot of people trying to use it, though there could certainly be a control issue (i.e not wanting to allow people to do "too much" on heroku)
[20:32:17] <kennethreitz> aclark: that doesn't answer my question
[20:32:31] <kennethreitz> aclark: I know all about buildout. But what can you not accomplish with pip?
[20:41:07] <aclark> kennethreitz: well i'm trying to answer without generalizing around plone which currently uses plone but may not always. if you know all about it then you already know what you can't accomplish, they are different tools. I can't write ini-style configs, i can't build configs from templates, I can't build non-python software, etc.