On 5/14/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 04:19 PM 5/14/2007 -0700, Guido van Rossum wrote:
> >But can you at least share enough of the problem so others can look at
> >it and either suggest a solution or agree with your conclusion?
>
> Sure. Take a look at peak.rules.core (while keeping in mind all the
> bits that will be changed per your prior requests):
>
> http://svn.eby-sarna.com/PEAK-Rules/peak/rules/core.py?view=markup
>
> What you'll notice is that the method combination framework (Method,
> MethodList, combine_actions, always_overrides, and merge_by_default,
> if you don't count the places these things get called) is in fact
> most of the code, with relatively little of it being the actual
> implementation of Around, Before, or After (or even generic functions
> themselves!).
Seems to me that from this link what we're missing is a good
explanation of how "Method" works since that is the base for Before,
After, etc. Thus I'd suggest ripping out the Before, After, etc.
sections in the PEP, and replacing them with a section on how Method
works. You can use Before and After as examples of how to extend
Method.
(I'm fine with Before and After being in the module. It's just
confusing that they take such a prominent role in the PEP without the
mechanism behind them being explained enough.)
STeVe
--
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
--- Bucky Katt, Get Fuzzy
_______________________________________________
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
