[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fab-user] api.run: fatal errors versus exceptions
From: |
Paul Hoffman |
Subject: |
[Fab-user] api.run: fatal errors versus exceptions |
Date: |
Tue, 17 Jan 2012 17:48:14 -0800 |
Greetings again. Some things that go wrong in api.run cause Python to
abort, instead of just throwing an exception. For example, "/bin/bash:
not found" causes the calling program to die, instead of (what I
expected) an exception that could be caught and analyzed.
Is this intentional? If not, is it easy to fix?
--Paul Hoffman
- [Fab-user] api.run: fatal errors versus exceptions,
Paul Hoffman <=
- Re: [Fab-user] api.run: fatal errors versus exceptions, Jeff Forcier, 2012/01/18
- Re: [Fab-user] api.run: fatal errors versus exceptions, Paul Hoffman, 2012/01/18
- Re: [Fab-user] api.run: fatal errors versus exceptions, Steve Hajducko, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Paul Hoffman, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Jeff Forcier, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Jeff Forcier, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Paul Hoffman, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Robert Terhaar, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Paul Hoffman, 2012/01/19
- Re: [Fab-user] api.run: fatal errors versus exceptions, Jeff Forcier, 2012/01/19