virtualenvwrapper-win
virtualenvwrapper-win copied to clipboard
PyPy support
I'm trying to use PyPy as my Python implementation of choice, but I'm having some issues. It looks like the batch files are using ENV\Scripts, but for some reason PyPy (and virtualenv under PyPy?) likes to use ENV\bin instead. Is there a way to check for existence of Scripts, then bin, and prefer that order?
Just installed pypy to check it out. You're right. Hooray for ignoring convention. I'll put this on my list. Always happy to get pull requests!
@mlaccetti I've created branch with experimental mkvritualenv support for pypy. If you could test is it would be great. https://github.com/davidmarble/virtualenvwrapper-win/tree/pypy_support
There are still issues with workon. But mkvirtualenv should work.
@utek I'll take it for a spin when I'm at my windows machine; sitting in front of a Mac 9-5.
@mlaccetti After looking at it more. I don't think that I did it good. Still a lot to do. But I don't have time now (neither I use pypy at the moment)
The pypy folder in Env is created with bin folder. Renaming bin folder to Scripts manually fixes the workon issue.