On Fri, 30 Nov 2007 11:35:18 +0100, Christian Heimes <[EMAIL PROTECTED]> wrote: >Dirkjan Ochtman wrote: >> I don't know how hard it would be for Jython, IronPython et al. to >> support this kind of interface, but seeing as how something like >> zope.interface relies on it (and therefore all of Twisted, too, I >> think), it's kind of mandatory anyway. > >zope.interface could work without sys._getframe(). It's not mandatory >for its API. getframe is used for a clever hack which makes declaring >interfaces more convenient and readable. > >class Example: > implements(IExample) >
This is a current feature of zope.interface. Therefore, zope.interface requires it, unless you can show an implementation of this API which does not depend on it. It is certainly true that this API could be removed from zope.interface. At that time, zope.interface would not depend on these frame APIs. It would also break almost every user of zope.interface and require them to change to the new API. Don't try to mix "could work" with "does work" together. Jean-Paul _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
