Message177163
There is one typo and one error in the first paragraph of the patch:
> When raising a new exception (rather than
> using to bare ``raise`` to re-raise the
^ should be an 'a'
> exception currently being handled), the
> implicit exception chain can be made explicit
> by using :keyword:`from` with :keyword:`raise`.
> The single argument to :keyword:`from` must be
> an exception or ``None``. It will be set as
> :attr:`__cause__` on the raised exception.
> Setting :attr:`__cause__` also implicitly sets
> the :attr:`__suppress_context__` attribute to ``True``.
The last sentence is incorrect -- __suppress_context__ is only set to True if __cause__ is set to None; if __cause__ is set to any other exception __suppress_context__ remains False and the new exception chain will be printed:
>>> try:
... raise ValueError
... except:
... raise NameError from KeyError
...
KeyError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "<stdin>", line 4, in <module>
NameError
This is easily fixed by adding 'to ``None``':
> Setting :attr:`__cause__` to ``None`` also implicitly sets
> the :attr:`__suppress_context__` attribute to ``True``. |
|
Date |
User |
Action |
Args |
2012-12-08 16:59:16 | ethan.furman | set | recipients:
+ ethan.furman, georg.brandl, ncoghlan, Arfrever, python-dev, Tyler.Crompton |
2012-12-08 16:59:16 | ethan.furman | set | messageid: <1354985956.6.0.815394333998.issue15209@psf.upfronthosting.co.za> |
2012-12-08 16:59:16 | ethan.furman | link | issue15209 messages |
2012-12-08 16:59:16 | ethan.furman | create | |
|