Skip to content

Commit 5f2d76c

Browse files
committed
Remove outdated note
1 parent 31f39a0 commit 5f2d76c

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

docs/source/start/updates.rst

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -96,14 +96,3 @@ to do so is by decorating your callback function with the :meth:`~pyrogram.Clien
9696
9797
9898
app.run()
99-
100-
101-
.. note::
102-
103-
Due to how these decorators work in Pyrogram, they will wrap your defined callback function in a tuple consisting of
104-
``(handler, group)``; this will be the value held by your function identifier (e.g.: *my_function* from the example
105-
above).
106-
107-
In case, for some reason, you want to get your own function back after it has been decorated, you need to access
108-
``my_function[0].callback``, that is, the *callback* field of the *handler* object which is the first element in the
109-
tuple, accessed by bracket notation *[0]*.

0 commit comments

Comments
 (0)