The update works. Although there should be some kind of indication that the virtual environment is activated or not. It is confusing without some indication of virtual environment.
@h4xr: I am not sure that I understand you. It's not necessary to activate virtual environment to use vex. If you use it with existing virtualenv vex execute command in this environment and if this virtualenv doesn't exist vex gives you and error message.
existing virtualenv test:
$ vex test pip freeze
tinyrpc==0.5
nonexisting virtualenv test2
$ vex test2 pip freeze
Error: no virtualenv found at '/builddir/.virtualenvs/test2'.
This update has been submitted for testing by lbalhar.
This update has been pushed to testing.
lbalhar edited this update.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi.
The update works. Although there should be some kind of indication that the virtual environment is activated or not. It is confusing without some indication of virtual environment.
@h4xr: I am not sure that I understand you. It's not necessary to activate virtual environment to use vex. If you use it with existing virtualenv vex execute command in this environment and if this virtualenv doesn't exist vex gives you and error message.
existing virtualenv test:
nonexisting virtualenv test2
This update has been pushed to stable.