[issue30292] Why is there a concept "unbound method" in <Descriptor HowTo Guide> python3 version?

New submission from debuggy: When I read <Descriptor HowTo Guide> (python 3.6.1 version), I found there is a concept of 'unbound method' in some places. However, when I referred to <What’s New In Python 3.0>, it said the concept of “unbound methods” has been removed from the language. So I wondered if there should be a change in <Descriptor HowTo Guide> python3 version? For instance, in this code example of the guide:
When I tested myself, the result of statement "D.f" should be <function> not <unbound method>. ---------- assignee: docs@python components: Documentation messages: 293160 nosy: debuggy, docs@python priority: normal severity: normal status: open title: Why is there a concept "unbound method" in <Descriptor HowTo Guide> python3 version? type: enhancement versions: Python 3.6 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue30292> _______________________________________

Changes by Martin Panter <vadmium+py@gmail.com>: ---------- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> docs.python.org/3/howto/descriptor.html still refers to "unbound methods" _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue30292> _______________________________________

Changes by Martin Panter <vadmium+py@gmail.com>: ---------- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> docs.python.org/3/howto/descriptor.html still refers to "unbound methods" _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue30292> _______________________________________
participants (2)
-
debuggy
-
Martin Panter