Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Ian Kelly <ian.g.kelly@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Meta decorator with parameters, defined in explicit functions
Date: Sun, 3 Jul 2016 18:01:21 -0600
Lines: 33
Message-ID: <mailman.52.1467590530.2295.python-list@python.org>
References: <85mvm5vrbw.fsf@benfinney.id.au> <mailman.61.1467090177.2358.python-list@python.org> <21916e7b-9e19-4cef-94e0-bac331540ca2@googlegroups.com> <CALwzidn8DuSo-L2UQTJ7wZfzK+eHGzgGuy_ZfHFR9v4J_NHnjQ@mail.gmail.com> <mailman.15.1467436194.2295.python-list@python.org> <facf7142-25f5-4a8b-ab37-771884ab8d64@googlegroups.com> <CALwzid=GfLU8nbc5m4M9FxEO1ObWDTcvLJ3-wJXS0=w88-v8sw@mail.gmail.com> <mailman.33.1467521333.2295.python-list@python.org> <46690e10-1534-4f99-a40f-a148b4a21a27@googlegroups.com> <CALwzidmn-0TyxfKxcZoNoV5CgiFuOqRS_X=W34gSn5a-NVOy_w@mail.gmail.com> <mailman.38.1467546815.2295.python-list@python.org> <d2f71d72-d2da-4f68-9d6a-ca059327afdd@googlegroups.com> <CALwzid=ZsBnqjcMHVU6YQ17_993z01K3wKZ2QwZb9LKF_KJt_A@mail.gmail.com> <mailman.47.1467585556.2295.python-list@python.org> <62b43f29-e6ea-4d19-9e9f-1becb3988bd3@googlegroups.com> <CALwzidn_Dxt8wuJ4dFdASkZ8Thmey4hMKXVLkXJGTiyt034A1g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <62b43f29-e6ea-4d19-9e9f-1becb3988bd3@googlegroups.com>
Precedence: list
Xref: csiph.com comp.lang.python:111025

On Sun, Jul 3, 2016 at 5:25 PM, Lawrence D=E2=80=99Oliveiro
<lawrencedo99@gmail.com> wrote:
> On Monday, July 4, 2016 at 10:39:30 AM UTC+12, Ian wrote:
>> Sorry, but you're the one who doesn't seem to get it. Because it's a
>> decorator, "your" function is replacing the caller's function in the
>> caller's namespace.
>
> No it is not. The replacement happens here:
>
>         def generated_decorator(func) :
>             return \
>                 decorator(func, *args, **kwargs)
>         #end generated_decorator
>
> As you can see, the function being called, =E2=80=9Cdecorator=E2=80=9D, i=
s supplied by the caller. The function being decorated, =E2=80=9Cfunc=E2=80=
=9D, is supplied by the caller (along with the additional *args and **kwarg=
s). And the returned function is returned *as-is*, so whatever docstring wa=
s assigned by the caller is *NOT* =E2=80=9Cclobbered=E2=80=9D.

I'm talking about the docstring of the *decorator*, not func. I agree
that whatever docstring func has is entirely up to func and the
decorator, not your code. Here again is the example I posted earlier:

>>> @decorator_with_args
... def my_decorator(func, *args, **kwargs):
...     """Returns func unmodified."""
...     return func
...
>>> my_decorator.__doc__
'generates a decorator which applies my_decorator to the given arguments'

I never made any claim about the docstring of the decorated func.