On Sat, Mar 22, 2008 at 12:51 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > If there's some chance it would be accepted, I would happily make the > patch. > > I don't think there is. Making it a keyword now means essentially to > agree that the feature will be added later, so opponents of the feature > will oppose the first step.
In any case, calling it "pragma" is C-damage. ;) There is no way you can understand what that is supposed to do unless you have used enough C to use #pragmas, more or less. I find the syntax from __future__ import <whatever> clearer. It tells you what it does: It imports a bit of the future. I dont' think there will be much use of other "pragmas", we don't WANT to change the languages behaviour except when backwards compatibility breaks. But if that happens at least call it something reasonable. As "enable specialfeature" or "use specialfeature". "pragma specialfeature" is just confusing. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
