{"action":"created","issue":{"url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/25","labels_url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/25/comments","events_url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/25/events","html_url":"https://github.com/yyuu/pyenv-virtualenvwrapper/issues/25","id":94750474,"number":25,"title":" pyenv is awesome but...","user":{"login":"lifeBalance","id":3051496,"avatar_url":"https://avatars.githubusercontent.com/u/3051496?v=3","gravatar_id":"","url":"https://api.github.com/users/lifeBalance","html_url":"https://github.com/lifeBalance","followers_url":"https://api.github.com/users/lifeBalance/followers","following_url":"https://api.github.com/users/lifeBalance/following{/other_user}","gists_url":"https://api.github.com/users/lifeBalance/gists{/gist_id}","starred_url":"https://api.github.com/users/lifeBalance/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lifeBalance/subscriptions","organizations_url":"https://api.github.com/users/lifeBalance/orgs","repos_url":"https://api.github.com/users/lifeBalance/repos","events_url":"https://api.github.com/users/lifeBalance/events{/privacy}","received_events_url":"https://api.github.com/users/lifeBalance/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-07-13T15:40:10Z","updated_at":"2015-07-13T22:43:10Z","closed_at":"2015-07-13T21:09:59Z","body":"Is there a way of not having to issue the command ``$ pyenv virtualenvwrapper`` every time I want to start working with my environments?\r\nI have been a long time user of **virtualenv** and **virtualenvwrapper**, where it wasn't neccessary to do that, just ``workon`` to list environments and start working. \r\n"},"comment":{"url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/comments/121082406","html_url":"https://github.com/yyuu/pyenv-virtualenvwrapper/issues/25#issuecomment-121082406","issue_url":"https://api.github.com/repos/yyuu/pyenv-virtualenvwrapper/issues/25","id":121082406,"user":{"login":"lifeBalance","id":3051496,"avatar_url":"https://avatars.githubusercontent.com/u/3051496?v=3","gravatar_id":"","url":"https://api.github.com/users/lifeBalance","html_url":"https://github.com/lifeBalance","followers_url":"https://api.github.com/users/lifeBalance/followers","following_url":"https://api.github.com/users/lifeBalance/following{/other_user}","gists_url":"https://api.github.com/users/lifeBalance/gists{/gist_id}","starred_url":"https://api.github.com/users/lifeBalance/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lifeBalance/subscriptions","organizations_url":"https://api.github.com/users/lifeBalance/orgs","repos_url":"https://api.github.com/users/lifeBalance/repos","events_url":"https://api.github.com/users/lifeBalance/events{/privacy}","received_events_url":"https://api.github.com/users/lifeBalance/received_events","type":"User","site_admin":false},"created_at":"2015-07-13T22:43:09Z","updated_at":"2015-07-13T22:43:09Z","body":"To many anyways... Anyway, I don't think **virtualenv/pyenv-virtualenv** would be an enhancement over **virtualenvwrapper/pyenv-virtualenvwrapper**,  just the opposite. If I have to take a wild guess, I'd say you haven't use **virtualenvwrapper** much, if you want, you can check the documentation [here](http://virtualenvwrapper.readthedocs.org/en/latest/) to see all its features. In any case, there are a lot of people using it because it's a great tool. Even projects like [virtualenv-burrito](https://github.com/brainsik/virtualenv-burrito) with more than 500 stars, are built on  top of **virtualenv + virtualenvwrapper**.\r\nAnyways, thanks for the info about adding ``pyenv virtualenvwrapper`` to my shell configuration, maybe not being present in the **README** was my issue ;)"}}