Message169325
| Author |
ncoghlan |
| Recipients |
Arfrever, ezio.melotti, georg.brandl, mark.dickinson, ncoghlan, rhettinger, skrah, zach.ware |
| Date |
2012年08月29日.01:37:13 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1346204234.72.0.592747386065.issue15783@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I agree it's an acceptable risk for 3.3.0. Most third party decimal operations simply won't accept an explicit context argument at all - avoiding the need to pass the current context around explicitly is the whole point of it being stored in the thread locals.
However, I still think it would be better if consistency with the Python API could be restored for 3.3.1. If that's done via a more general "this value means the arg is actually missing" C API that can be made public in 3.4, so much the better. |
|