Thanks. I think the catching SystemExit hack works for me. CC mailing list.
On Tue, Apr 9, 2013 at 9:51 AM, Jeff Forcier <[email protected]> wrote: > Hi Zhigang, > > This is more appropriate for the mailing list -- emailing the dev > directly when a list exists is sometimes considered rude ;) > > That said, I want to limit the number of options & behaviors we add to > fabric 1.x (Fabric 2.x will use far more exceptions for this sort of > thing, thus easily catchable) so I'm not sure adding this extra layer > of "failing" is worth the tradeoff. > > However, you can currently catch "aborts" by using an "except > SystemExit". It's a bit of a hack, of course, but it does function > pretty well. > > -Jeff > > On Tue, Apr 9, 2013 at 9:22 AM, Zhigang Wang <[email protected]> wrote: > > Hi Jeff, > > > > Sorry to disturb you. > > > > I just tried using fabric as a library. One issue I cannot figure out: I > > need it just fail (not abort my program) on prompts. > > > > How can I do this? Or we need a patch to add an option like: > > env.fail_on_prompts ? > > > > Let me know if you want me to file a issue for this. > > > > Thanks, > > > > Zhigang > > > > > > -- > Jeff Forcier > Unix sysadmin; Python/Ruby engineer > http://bitprophet.org >
_______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
