<div class="gmail_quote">On 3 February 2012 15:02, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Both will be allowed - in 3.x, '...' is just an ordinary expression</div>
that means exactly the same thing as the builtin Ellipsis:<br>
<br>
>>> Ellipsis<br>
Ellipsis<br>
>>> ...<br>
Ellipsis<br></blockquote><div><br></div><div>I'd totally forgotten that was the case in 3.x ... it's still not exactly common to use Ellipsis/... directly except in extended slicing.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sane code almost certainly won't include *either* form, though. If<br>
you're reraising an exception, you should generally be leaving<br>
__cause__ and __context__ alone, and if you're raising a *new*<br>
exception, then __cause__ will already be Ellipsis by default - you<br>
only need to use "raise X from Y" to set it to something *else*.<br></blockquote><div><br></div><div>Absolutely - I can't think of a reason to want to reraise an existing exception while supressing any existing __cause__ in favour of __context__. But I'm sure someone can.</div>
<div><br></div><div>Tim Delaney</div></div>