Jim Jewett wrote: > On 5/12/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote: >> At 01:43 PM 5/12/2007 +1200, Greg Ewing wrote: > >> In practice, @around is mostly used for application-defined special >> cases, and there is no higher authority than the application who >> needs to override things. If a library needs special combinators >> internally, it's better off making them [EMAIL PROTECTED] >> precedence. Normal, before, and after methods are usually adequate >> for libraries. (Aside from special-purpose combinators like the >> @discount example.) > > (1) Would it be reaonable to say this in the PEP? > > (2) Would it be reasonable to leave out (or at least, leave for > another PEP) the extension methods like discount?
There ought to be a way to preserve with each PEP a separate document containing a more lengthy discussion of the rationales and consequences. Similar to the way that the _Federalist Papers_ is often used to interpret the meaning of the U.S. Constitution. > -jJ > _______________________________________________ > 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/talin%40acm.org _______________________________________________ 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
