-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abandoned? #102
Comments
I am all for it. I had to fork the project in order to incorporate some (very light) changes. But I would definitely prefer a community solution. And be glad to be part of it. The author had put a link on the README to another fork which has other interesting features. However, this one seems also to be unmaintained (I might be wrong). I have just started the process to review some of the pull request of this repo to be added back in my fork. Would you (anyone else too) be interested in doing it with me? I will add as collaborators. |
Yeah pythonz looks really good, but as you said, looks a bit abandoned too. 3.3 is still not supported in pythonz. Sounds great, I could help out on my spare time, though it's not a lot at the moment. |
It seems like @utahta is updating again!!!! So awesome!!!! I've used vanilla virtualenv += wrapper, virtualenv-burrito and pythonbrew. I really like pythonbrew as it seems most like rvm. keeping everything separated is ideal... |
good news! |
Wihooo! |
The last commit is almost 8 months old now and Python 3.3 has been out for over two months. IMO pythonbrew is an important part of the community so this project can't just go on unmaintained.
Maybe we can add some collaborators so we can merge in pull requests. What do you guys think?
The text was updated successfully, but these errors were encountered: