Message162021
| Author |
alonho |
| Recipients |
alonho, ncoghlan |
| Date |
2012年05月31日.21:23:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1338499395.29.0.0675599021628.issue14969@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Another possible solution is to explicitly set an exception's __supress_context__ attribute to False (right now impossible because it's the default value).
If a user can 'turn on' the flag when attaching a different exception (raise X from Y), why not allow 'turning it off'? (symmetry anyone?) right now it is set to False by default and changed to true when 'raising from'.
I suggest changing the default to None, allowing the user to explicitly say: I'm no longer in the previous exception's context.
Feels a bit like solving our hack with another hack (:
And about the PSF contrib agreement, I'll do it as soon as I'm near a printer. too bad we're using pens and not RSA private keys for signatures (-:
thanks, Alon |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年05月31日 21:23:15 | alonho | set | recipients:
+ alonho, ncoghlan |
| 2012年05月31日 21:23:15 | alonho | set | messageid: <1338499395.29.0.0675599021628.issue14969@psf.upfronthosting.co.za> |
| 2012年05月31日 21:23:14 | alonho | link | issue14969 messages |
| 2012年05月31日 21:23:14 | alonho | create |
|