{"action":"opened","issue":{"url":"https://api.github.com/repos/Pylons/pyramid-cookiecutter-starter/issues/4","repository_url":"https://api.github.com/repos/Pylons/pyramid-cookiecutter-starter","labels_url":"https://api.github.com/repos/Pylons/pyramid-cookiecutter-starter/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/Pylons/pyramid-cookiecutter-starter/issues/4/comments","events_url":"https://api.github.com/repos/Pylons/pyramid-cookiecutter-starter/issues/4/events","html_url":"https://github.com/Pylons/pyramid-cookiecutter-starter/issues/4","id":190914857,"number":4,"title":"do not create a virtualenv","user":{"login":"mmerickel","id":487237,"avatar_url":"https://avatars.githubusercontent.com/u/487237?v=3","gravatar_id":"","url":"https://api.github.com/users/mmerickel","html_url":"https://github.com/mmerickel","followers_url":"https://api.github.com/users/mmerickel/followers","following_url":"https://api.github.com/users/mmerickel/following{/other_user}","gists_url":"https://api.github.com/users/mmerickel/gists{/gist_id}","starred_url":"https://api.github.com/users/mmerickel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmerickel/subscriptions","organizations_url":"https://api.github.com/users/mmerickel/orgs","repos_url":"https://api.github.com/users/mmerickel/repos","events_url":"https://api.github.com/users/mmerickel/events{/privacy}","received_events_url":"https://api.github.com/users/mmerickel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-22T06:03:28Z","updated_at":"2016-11-22T06:03:28Z","closed_at":null,"body":"I've been thinking about this as I dive into getting things sorted for an official release. There are several issues with having the cookiecutter automatically create a virtualenv that I want on the record before we go forward.\r\n\r\nFirst, the easy one.. the inconsistency that it doesn't work on Python 2.7. Not a big deal but definitely a con.\r\n\r\nSecond, the real issue to me is that the user no longer has control over which python is used for the scaffold. It's coupled to the python that cookiecutter is installed in, which can be hard to trace. For example, cookiecutter is installable from homebrew (`brew install cookiecutter`). This currently defaults to python2.7 and thus does not create a virtualenv.\r\n\r\nOn top of that the pre-hook says it will create a virtualenv (even when it won't - this obviously needs to be fixed either way). And, even when it does, the pre-hook doesn't pause to let the user know.. it's just a quick message that scrolls by so I'm not sure what the point of it is. Maybe it should at least ask the user if they want to create a virtualenv?\r\n\r\nIn general I do not think that having the cookiecutters create virtualenvs helps with the tutorial situation... in my opinion it probably makes them slightly harder to explain due to some of these things that can go wrong.\r\n\r\nFinally, there's very few cookiecutters that I've seen that try to do this and so it's not really expected by anyone - and doing things that are unexpected is usually not a good sign.\r\n\r\nWhat do other people think?"}}
{"actor":{"display_login":"mmerickel"}}