PEP318: radical notion

Arien Malec arien.malec at
Fri Aug 27 02:04:37 CEST 2004

Christophe Cavalaria <chris.cavalaria at> wrote in message news:<412d13bc$0$14159$636a15ce at>...
> Arien Malec wrote:
> > Christophe Cavalaria <chris.cavalaria at> wrote in
> > news:412bc7e6$0$4065$626a14ce at

> >> Why is it that there are always some people who doesn't understand all
> >> the possibilities of decorators and so want to minimise their
> >> usefulness ?
> > 
> > I dunno. Who are those people? My objection to PEP318 is that makes
> > something that's really powerful (arbitrary transformation) look like a
> > trivial declaration.
> If that's your objection, say it. I'm ok with that.

I did, see the top of this thread.

To be clear, I don't deny that autotransformers of module-scoped
functions wouldn't be quite useful; I'm queasy about using the same
syntax to add metadata AND mangle functions and methods.

My thought was that metadata + metaclasses gives the same ability as
PEP318 in a clean way to a suffiently large subset of use cases that
it's better to go with that and figure out separately how to perform
metaclass-like magic to module-scoped functions than it is to apply
the function autotransformation semantics to solve all problems.


More information about the Python-list mailing list