Tim Harig a écrit :
> On 2010-11-14, Camille Harang wrote:
>> # pg_dump prompts for password so I inject it in stdin.
>> pgsql.stdin.write('MY_PASSWORD' + '\n')
>
> For security reasons, some programs use direct access to the TTY system
> for password
Tim Harig a écrit :
> On 2010-11-14, Camille Harang wrote:
>> # pg_dump prompts for password so I inject it in stdin.
>> pgsql.stdin.write('MY_PASSWORD' + '\n')
>
> For security reasons, some programs use direct access to the TTY system
> for password
Hi Chris, thanks for your reply.
Chris Rebert a écrit :
> Quoting http://docs.python.org/library/subprocess.html , emphasis mine:
> """
> On Unix, with shell=True: [...] If args is a sequence, ***the first
> item*** specifies the command string, and any additional items will be
> treated as additi
Hi all,
I'm having a problem with subprocess.Popen. It seems that its unable to
capture the pg_dump's standard inputs & outputs in a non-shell mode:
from subprocess import Popen, PIPE
# fire pg_dump in order to read data from the file object pgsql.stdout
pgsql = Popen(['/usr/bin/pg_dump',
