Chris Angelico rosuav at gmail.com
Sat Jan 2 17:01:45 EST 2016

• Previous message (by thread): subprocess check_output
• Next message (by thread): subprocess check_output
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sun, Jan 3, 2016 at 7:39 AM, Carlos Barera <carlos.barera at gmail.com> wrote:
> Turns out it wasn't running against the server I thought it was.
> Apologies for the spam.

Heh. No problem. That's part of why I suggested running it from the
shell. There are two possibilities: either it also fails from the
shell (in which case you've eliminated Python as the problem, and can
concentrate on "why is my command not working"), or it succeeds when
run manually and still fails from Python (in which case you can start
investigating the differences). And every now and then, it's worth
doing a stupid smoke test just to see if your changes are even having
effect. You have no idea how many times a bug investigation has come
down to "whoops, I forgot to save the file" or "whoops, I was in the
wrong directory"...

ChrisA

---

• Previous message (by thread): subprocess check_output
• Next message (by thread): subprocess check_output
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list