I actually wrote the book _ Functional Programming in Python_, yet I haven't the foggiest idea how to parse that code. A decorator parameterized buy two instances of the decorator function itself?!
I know I could read the implementation and figure out why that works. But I don't want to encourage that code in real use. On Sep 20, 2016 11:17 AM, "Stephan Houben" <stephan...@gmail.com> wrote: > I must admit I am a bit partial to partial, you can do fun things like > this: > > >>> from functools import partial > >>> @partial(partial, partial) > ... def add(x, y): > ... return x+y > ... > >>> add(3)(4) > 7 > > I suppose that isn't exactly going to convince Guide to put it in > builtins, though. > > Stephan > > > > 2016-09-20 19:48 GMT+02:00 David Mertz <me...@gnosis.cx>: > >> I find myself "partializing" in ways partial() doesn't support more often >> than not. E.g. >> >> lambda first, third: myfunc(first, 42, third) >> >> I think it's good to have partial() in functools, but it's two orders of >> magnitude less common than things that should be in builtins. >> >> On Sep 20, 2016 9:42 AM, "Ryan Gonzalez" <rym...@gmail.com> wrote: >> > lambda *args, **kw: myfunc(partial_arg, *args, **kw) >> > >> > which isn't more readable than just: >> > >> > partial(myfunc, partial_func) >> >> _______________________________________________ >> Python-ideas mailing list >> Python-ideas@python.org >> https://mail.python.org/mailman/listinfo/python-ideas >> Code of Conduct: http://python.org/psf/codeofconduct/ >> > >
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
