Log file Viewer

[19:45:00] <stbatduke> Ohai!

[19:45:45] <stbatduke> Question: Is there a ''bash'' way to check if I am working within a virtualenv, and to check wich virtualenv I am working within?

[19:45:53] <stbatduke> I found the python way, but I need a bash way too :)

[19:57:21] <apollo13> VIRTUAL_ENV env var?

[19:57:28] <apollo13> at least if using virtualenvwrapper

[20:03:45] <carljm> no, that's part of virtualenv itself, not just virtualenvwrapper

[20:03:54] <carljm> (but only if you use the "activate" script)

[20:04:13] <carljm> of course, if you don't use "activate", then virtualenv has nothing to do with your shell, so...

[20:04:22] <apollo13> hehe

[20:08:33] <stbatduke> perfect!

[20:08:54] <stbatduke> echo $VIRTUAL_ENV worked like a charm

[20:09:22] <stbatduke> I'm new to this environment ... new job an' all ... as well as new to python

[20:09:40] <stbatduke> they use some script "workon" to run the activate command

[20:09:50] <stbatduke> is that part of virtualenvwrapper ?

[20:13:00] <apollo13> yes

[20:21:19] <stbatduke> tyty apollo13 and carljm !!!

[20:37:19] <stbatduke> another Another question: where are the mkvirtualenv and rmvirtualenv commands stored?

[20:37:44] <stbatduke> I can find pre and post mkvirtualenv ... but I don't understand where the main command is

[20:46:06] <stbatduke> now I'm really confused, "sudo find / -name virtualenvwrapper.sh" returned nothing.