Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #65805 > unrolled thread

Re: Using virtualenv to bypass sudoer issues

Back to article view | Back to comp.lang.python

Contents

  Re: Using virtualenv to bypass sudoer issues Jean-Michel Pichavant <jeanmichel@sequans.com> - 2014-02-10 11:06 +0100
    Re: Using virtualenv to bypass sudoer issues Pete Forman <petef4+usenet@gmail.com> - 2014-02-10 14:23 +0000

#65805 — Re: Using virtualenv to bypass sudoer issues

Thank you all for you insights.

I'll probably go with virtualenv, I'll be able to distribute it among the team.
There's still one point worrying me though:
We're doing a lot a remote execution. We're using "execnet" http://codespeak.net/execnet/, and I'm not sure it can be compatible with virtualenv. execnet working at the "python level" I don't see how I can execute shell stuff before.

I had a look at fabric http://docs.fabfile.org/en/1.8/, and it looks like it can handle virtual env (anyone confirm?).

Has someone already successfully remotely activated a venv then execute a python scripts within that env, getting back the stdout/stderr ?

I'm afraid right now that switching to venv would mean switching from execnet to fabric as well (I hate redoing stuff that works :-/ ).

JM  


-- IMPORTANT NOTICE: 

The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[toc] | [next] | [standalone]

#65816

Jean-Michel Pichavant <jeanmichel@sequans.com> writes:

> Thank you all for you insights.
>
> I'll probably go with virtualenv, I'll be able to distribute it among
> the team.
> There's still one point worrying me though:
> We're doing a lot a remote execution. We're using "execnet"
> http://codespeak.net/execnet/, and I'm not sure it can be compatible
> with virtualenv. execnet working at the "python level" I don't see how
> I can execute shell stuff before.
>
> I had a look at fabric http://docs.fabfile.org/en/1.8/, and it looks
> like it can handle virtual env (anyone confirm?).
>
> Has someone already successfully remotely activated a venv then
> execute a python scripts within that env, getting back the
> stdout/stderr ?
>
> I'm afraid right now that switching to venv would mean switching from
> execnet to fabric as well (I hate redoing stuff that works :-/ ).

Call the venv version of python and activation is handled.
E.g. in a fabfile

    myenv/bin/python myscript.py

-- 
Pete Forman

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web