This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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:15alonhosetrecipients: + alonho, ncoghlan
2012-05-31 21:23:15alonhosetmessageid: <1338499395.29.0.0675599021628.issue14969@psf.upfronthosting.co.za>
2012-05-31 21:23:14alonholinkissue14969 messages
2012-05-31 21:23:14alonhocreate