Incorrect description about scope related with inheritance

@bitdancer

BPO	29010
Nosy	@bitdancer, @brendan-donegan, @brendan-donegan

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2016-12-19.04:45:33.115>
labels = ['easy', '3.11', '3.9', '3.10', 'docs']
title = 'Incorrect description about scope related with inheritance'
updated_at = <Date 2021-11-19.17:34:43.264>
user = 'https://bugs.python.org/wooyoo'

bugs.python.org fields:

activity = <Date 2021-11-19.17:34:43.264>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-12-19.04:45:33.115>
creator = 'woo yoo'
dependencies = []
files = []
hgrepos = []
issue_num = 29010
keywords = ['easy', 'newcomer friendly']
message_count = 12.0
messages = ['283580', '283581', '283596', '283621', '283622', '283623', '283663', '283666', '283667', '283691', '283694', '283696']
nosy_count = 5.0
nosy_names = ['r.david.murray', 'docs@python', 'woo yoo', 'brendan-donegan', 'brendand']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue29010'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

The current description is "The name BaseClassName must be defined in a scope containing the derived class definition", which did not conform to the actual situation ,e.g. the base class object is not in the same scope as the derived class.

The associated link is https://docs.python.org/3.6/tutorial/classes.html#inheritance

Hi. Can you please provide a small code snippet illustrating where this diverges from the actual behaviour?

Code:

class A(object):
pass

'object' is not in the same scope as 'A'

It is part of the global scope, which contains all other scopes. (I'm not 100% sure I'm comfortable with that language, but it doesn't seem obviously wrong.)

The previous description about scope classify it into 3 types explicitly, which means the scope containing the current module's global names is not same as the scope containing built-in names.

If i was wrong about this issue, please tell me.

IMO there's no actual bug in Python. Perhaps documentation can be clarified
in a short simple way. I would reiterate the point that restating facts of
the language all over the documentation is not a great idea, but maybe here
the benefits outweigh the drawbacks.

Anyway I think the bug is clear now (it's a docs issue if anything) so I'd
leave it open until someone offers a patch or a strong argument why it
shouldn't be clarified.

On Tue, 20 Dec 2016 at 09:18 woo yoo <report@bugs.python.org> wrote:

woo yoo added the comment:

If i was wrong about this issue, please tell me.

----------

Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue29010\>

I agree with you

Would it make it clearer if we said "BaseClassName must be defined in a namespace accessible from the scope containing the dervied class definition" ?

Worth putting them side by side I think:

"The name BaseClassName must be defined in a scope containing the derived class definition"

vs.

"BaseClassName must be defined in a namespace accessible from the scope containing the derived class definition"

As for me, i prefer the new description, which is clear and easy to understand.

gh-73196: Add namespace/scope clarification for inheritance section (#…

Merge branch 'main' into typewatch

pythongh-73196: Add namespace/scope clarification for inheritance sec…

Navigation Menu

Repository navigation

Incorrect description about scope related with inheritance #73196

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Incorrect description about scope related with inheritance #73196

Description

Activity

wooyoo commented on Dec 19, 2016

wooyoo commented on Dec 19, 2016

brendan-donegan commented on Dec 19, 2016

wooyoo commented on Dec 19, 2016

bitdancer commented on Dec 19, 2016

wooyoo commented on Dec 19, 2016

wooyoo commented on Dec 20, 2016

brendan-donegan commented on Dec 20, 2016

wooyoo commented on Dec 20, 2016

bitdancer commented on Dec 20, 2016

brendan-donegan commented on Dec 20, 2016

wooyoo commented on Dec 20, 2016

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions