Nick Coghlan ncoghlan at gmail.com
Sun May 20 10:53:08 CEST 2012

• Previous message: [Python-Dev] PEP 3135 (new super()) __class__ references broken in 3.3
• Next message: [Python-Dev] PEP 3135 (new super()) __class__ references broken in 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sun, May 20, 2012 at 6:51 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> What I plan to do:
> 1. Revert the previous fix for #12370
> 2. Add tests for direct access to __class__ from methods
> 3. Create a *new* fix for #12370 that only affects the class scope,
> not the method bodies (this will be harder than the previous fix which
> affected the resolution of __class__ *everywhere* in the class body).

Correction - I only plan to *reopen* #12370. I agree it's a legitimate
problem with the PEP 3135 implementation, but at least it's not a
regression for something that previously worked in 3.2.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message: [Python-Dev] PEP 3135 (new super()) __class__ references broken in 3.3
• Next message: [Python-Dev] PEP 3135 (new super()) __class__ references broken in 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list