I created a patch against the trunk, tested it and attached to the newly created ticket 310.<div><br></div><div>Hopefully you will find it useful</div><div><br></div><div>Best regards<br><br><div class="gmail_quote">On Wed, Apr 28, 2010 at 00:23, Daniel Rodriguez <span dir="ltr">&lt;<a href="mailto:danjrod@gmail.com">danjrod@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Jeff,<div><br></div><div>I was reworking the error managing of the library I have built on top of Suds and I think that the Exceptions raised by Suds could be reworked to allow a finer &quot;catching&quot; granularity, without impacting the current system.</div>

<div><br></div><div>I assume that Suds does only raise exceptions defined in suds/__init__.py and then:</div><div><ul><li>All defined exceptions but WebFault belong to the pre-network stage.</li><li>WebFault belongs to the the post-network stage (suds can only detect a &quot;webfault&quot; once it has seen the answer from the server</li>

</ul><div>It is obvious, in my opinion, that some people would like to treat those 2 groups of exceptions differently and maybe have just to &quot;excepts&quot; handling the potential cases. But this is difficult, given that all exceptions are derived from &quot;Exception&quot;.</div>

<div><br></div><div>An initial proposal would then be:</div><div><ul><li>Have a &quot;SudsError&quot; (derived from Exception) that will act as a base class for all Suds exceptions.</li><li>Derive (obviously) all exceptions from &quot;SudsError&quot;</li>

</ul><div>This would allow implementing the following:</div><div><br></div></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><div>try:</div><div>  mysudsclient.callmethod(param)</div>
<div>except suds.WebFault as wf:</div><div>  doSomethingWithTheWebFault(wf)</div><div>except suds.SudsError as se:</div><div>  doSomethingWithSudsError(se)</div><div>except Exception as ex:</div><div>  doSomethingWithRegularPythonException(ex)</div>

<div><br></div></div></div></blockquote><div>Even standard SudsError exceptions can be separated from standard Python Exceptions and handled separately.</div><div><br></div><div>This is, again in my opinion, straightforward and poses no change to the existing interface, while delivering (as stated above) a greater  control over exception handling in suds.</div>

<div><br></div><div>I can implement a patch if you think that this approach is something interesting for suds.</div><div><br></div><div>Best regards</div><div><br></div><font color="#888888"><div>Daniel</div><div><br></div>
<div><br></div>
</font></blockquote></div><br></div>