missing deactivate from virtualenv - nupic-linux64

[breznak]

@oxtopus I need to run virtualenv to get proper version of python, to quit from there it provides deactivate (shell function? it's not a file). Yet, if I run source nupic-linux64/bin/activate in there to get to use this repo, the deactivate works only once (get's me out of nupic-linux64 env..probably?), and I'm stuck in the python env w/o any means to exit. I need to close whole shell session.

Should nupic-linux64 provide it's own version of deactivate, so these stack up and i have 1 for nupic-linux64 and 1 for python env?

Thanks!

[oxtopus]

That sounds reasonable. It'd be trivial to rename the command to something
unique to nupic and it's early enough that such a change wouldn't cause
much disruption.

On Wednesday, October 30, 2013, breznak wrote:

@oxtopus https://github.com/oxtopus I need to run virtualenv to get
proper version of python, to quit from there it provides deactivate (shell
function? it's not a file). Yet, if I run source nupic-linux64/bin/activate
in there to get to use this repo, the deactivate works only once (get's me
out of nupic-linux64 env..probably?), and I'm stuck in the python env w/o
any means to exit. I need to close whole shell session.

Should nupic-linux64 provide it's own version of deactivate, so these
stack up and i have 1 for nupic-linux64 and 1 for python env?

Thanks!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/366
.

[breznak]

👍 thank you, that'd be great.

[breznak]

already fixed by @oxtopus in 9e4df07ee03184d670a88, thank you! (PS: I noticed just now, didnt know you fixed it aready :) )
@rhyolight this bug is successfully resolved. Closing.