Closed jdevera closed 10 years ago
Thanks for reporting the error and particularly for including a traceback. So this happens if people try to use vex --shell-config without making a virtualenv, setting up manually or having used another tool like virtualenvwrapper before. I'll leave the assert as it is, because it's a safeguard which clearly told me the story, and the condition you encountered shouldn't happen now anyway.
It's not going to be a killer bug or occur for most people, so I am going to wait on doing a new version release until I have cleared out any other immediate pending issues. It shouldn't be more than a few days at maximum. But I pushed the solution to this to github, so this is fixed as of 93d39dabe32c2e9ab5c717311ddcb078471bce53.
The other issue is a WIndows thing that likely depends on an upstream bug in virtualenv, so I pushed a new version 0.0.11 for this. Have fun.
I'm trying vez for the first time, I try to run:
And I get this:
I only found out that the problem was my missing
~.virtualenvs
until I poked in the code. But I'd suggest having a human readable error for this case.