➜

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 barry
Recipients Arfrever, BreamoreBoy, barry, benjamin.peterson, christian.heimes, georg.brandl, larry, nailor, pitrou, python-dev
Date 2013-09-29.17:24:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380475498.11.0.293789227593.issue16037@psf.upfronthosting.co.za>
In-reply-to
Content 
As we discussed in other issues regarding the similar problem, I don't really want to introduce a new exception in a point release of 2.6.  Is there any reason not to just raise HTTPException with the error message text?  Code that has to work across multiple 2.6.X versions won't be able to import the new exception, and thus cannot rely on it anyway.

If you agree, I'll make that change when I apply this patch.
History
Date User Action Args
2013-09-29 17:24:58barrysetrecipients: + barry, georg.brandl, pitrou, larry, christian.heimes, benjamin.peterson, Arfrever, BreamoreBoy, nailor, python-dev
2013-09-29 17:24:58barrysetmessageid: <1380475498.11.0.293789227593.issue16037@psf.upfronthosting.co.za>
2013-09-29 17:24:58barrylinkissue16037 messages
2013-09-29 17:24:57barrycreate