On 4/28/07, Calvin Spealman <[EMAIL PROTECTED]> wrote: > Comments welcome, of course. Bare with my first attempt at crafting a PEP. > > PEP: XXX > Title: Super As A Keyword > Version: $Revision$ > Last-Modified: $Date$ > Author: Calvin Spealman <[EMAIL PROTECTED]> > Status: Draft > Type: Standards Track > Content-Type: text/x-rst > Created: 30-Apr-2007 > Python-Version: 2.6 [snip] > Which means the backward compatible API, which involves instansiating the > super > type, will either not be possible, because it will actually do a super lookup > on the __call__ attribute, or there will be no way to perform a super lookup > on > the __call__ attribute. Both seem unacceptable, so any suggestions are > welcome.
You're offering absolutely zero backwards compatibility and you're targeting 2.6? Um, no; absolutely not. Even if you intend this for 3.0, you'll still need to define either a backwards compatibility solution or a migration strategy (e.g., a 2to3 fixer). Without a clear-cut way of addressing existing code, this idea is toast. Collin Winter _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com