[Python-Dev] The decorator(s) module
Crutcher Dunnavant
crutcher at gmail.com
Sat Feb 11 19:33:45 CET 2006
More information about the Python-Dev mailing list
Sat Feb 11 19:33:45 CET 2006
- Previous message: [Python-Dev] The decorator(s) module
- Next message: [Python-Dev] PEP 338 - Executing Modules as Scripts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
+1, and we could maybe include tail_call_optimized? http://littlelanguages.com/2006/02/tail-call-optimization-as-python.html On 2/11/06, Georg Brandl <g.brandl at gmx.net> wrote: > Hi, > > it has been proposed before, but there was no conclusive answer last time: > is there any chance for 2.5 to include commonly used decorators in a module? > > Of course not everything that jumps around should go in, only pretty basic > stuff that can be widely used. > > Candidates are: > - @decorator. This properly wraps up a decorator function to change the > signature of the new function according to the decorated one's. > > - @contextmanager, see PEP 343. > > - @synchronized/@locked/whatever, for thread safety. > > - @memoize > > - Others from wiki:PythonDecoratorLibrary and Michele Simionato's decorator > module at <http://www.phyast.pitt.edu/~micheles/python/documentation.html>. > > Unfortunately, a @property decorator is impossible... > > regards, > Georg > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/crutcher%40gmail.com > -- Crutcher Dunnavant <crutcher at gmail.com> littlelanguages.com monket.samedi-studios.com
- Previous message: [Python-Dev] The decorator(s) module
- Next message: [Python-Dev] PEP 338 - Executing Modules as Scripts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list