Message202019
| Author |
ncoghlan |
| Recipients |
Jim.Jewett, Trundle, Yury.Selivanov, barry, benjamin.peterson, cvrebert, daniel.urban, eric.araujo, ethan.furman, gcbirzan, gvanrossum, jamesh, ncoghlan, pitrou, yorik.sar |
| Date |
2013年11月03日.12:36:15 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1383482175.66.0.921738404914.issue12029@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
A point on the safety/correctness front: I remembered we already run arbitrary code at roughly this point in the eval loop, as we have to invoke __iter__ to get the exceptions to check when an iterable is used in except clause.
That means allowing the subclass check hooks to run here isn't as radical a change as I first thought. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年11月03日 12:36:15 | ncoghlan | set | recipients:
+ ncoghlan, gvanrossum, barry, jamesh, pitrou, benjamin.peterson, eric.araujo, Trundle, cvrebert, daniel.urban, yorik.sar, ethan.furman, Yury.Selivanov, Jim.Jewett, gcbirzan |
| 2013年11月03日 12:36:15 | ncoghlan | set | messageid: <1383482175.66.0.921738404914.issue12029@psf.upfronthosting.co.za> |
| 2013年11月03日 12:36:15 | ncoghlan | link | issue12029 messages |
| 2013年11月03日 12:36:15 | ncoghlan | create |
|