Message161704
| Author | ncoghlan |
|---|---|
| Recipients | Arfrever, alex, barry, benjamin.peterson, daniel.urban, michael.foord, ncoghlan, python-dev |
| Date | 2012-05-27.08:22:30 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1338106951.16.0.585996222964.issue12370@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
As the checkin message says, this is once again a problem on trunk. The relevant test is still in place in test_super.py, I just marked it as an expected failure. unittest.mock is currently avoiding the problem via the "_safe_super = super" workaround. So, we need a new patch which fixes the misbehaviour *without* breaking the new tests I just added. I'm thinking something which special cases __class__ references in a ClassBlock to be dual purpose (i.e. both locals *and* closure variables) may be necessary, rather than the current approach of always coercing them to be closure variables. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-05-27 08:22:31 | ncoghlan | set | recipients: + ncoghlan, barry, benjamin.peterson, Arfrever, alex, michael.foord, daniel.urban, python-dev |
| 2012-05-27 08:22:31 | ncoghlan | set | messageid: <1338106951.16.0.585996222964.issue12370@psf.upfronthosting.co.za> |
| 2012-05-27 08:22:30 | ncoghlan | link | issue12370 messages |
| 2012-05-27 08:22:30 | ncoghlan | create | |