[issue8722] Documentation for __getattr__

Nick Coghlan added the comment: Thanks for the patch Cheryl, and for the reviews Terry! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue8722] Documentation for __getattr__

Nick Coghlan added the comment: New changeset fea0a12f6bee4a36b2c9533003e33a12c58d2d91 by Nick Coghlan (Miss Islington (bot)) in branch '3.7': [3.7] bpo-8722: Document __getattr__ behavior with AttributeError in property (GH-5543)

[issue8722] Documentation for __getattr__

Nick Coghlan added the comment: New changeset a8c25d1c7f0d395861cc3e10dd01989150891c95 by Nick Coghlan (Miss Islington (bot)) in branch '3.6': [3.6] bpo-8722: Document __getattr__ behavior with AttributeError in property (GH-5542)

[issue8722] Documentation for __getattr__

Change by miss-islington : -- pull_requests: +5369 ___ Python tracker ___

[issue8722] Documentation for __getattr__

Change by miss-islington : -- keywords: +patch pull_requests: +5368 ___ Python tracker ___

[issue8722] Documentation for __getattr__

Nick Coghlan added the comment: New changeset d1f318105b8781b01f3507d5cb0fd841b977d5f2 by Nick Coghlan (Cheryl Sabella) in branch 'master': bpo-8722: Document __getattr__ behavior with AttributeError in property (GH-4754)

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: Nick, this is about better documenting the behavior of __get(set/del)attr__ in 3.x it relations to AttributeError in a property. I think I understand what it does and think the patch is correct. Could you either review or suggest someone

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: Thanks. I normally look at source in my local clone with an editor. I found 'view blame' and 'view blame prior' on github. -- keywords: -patch ___ Python tracker

[issue8722] Documentation for __getattr__

Cheryl Sabella added the comment: >> Is there a way to get an annotated listing from git (given which patch, and >> therefore which person, is responsible for each line)? Which source did you want to look at? In github, if you go into any source, you can click on a line

[issue8722] Documentation for __getattr__

Change by Berker Peksag : -- keywords: +patch ___ Python tracker ___ ___

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: The behavior and doc for __setattr__ and __delattr__ should also be checked. -- ___ Python tracker

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: Before testing, let alone documenting, the status quo, I would like to be sure that suppressing the exception is truly the intended behavior. Is there a way to get an annotated listing from git (given which patch, and therefore which

[issue8722] Documentation for __getattr__

Cheryl Sabella added the comment: Terry, Thanks for clarifying with this example. I hadn't tried this when I was playing with the other example. I guess __getattribute__ might be defined by a class, but generally wouldn't be called directly, so the use of __getattr__ and

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: Cheryl, thank you for reviving this, as it is still needed. A slightly revised example better illustrates the claim in the doc revision about when __getattr__ is called. class Foo(object): def __init__(self): self.foo = 1

[issue8722] Documentation for __getattr__

Change by Cheryl Sabella : -- keywords: +needs review -patch versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker

[issue8722] Documentation for __getattr__

Change by Cheryl Sabella : -- pull_requests: +4657 stage: needs patch -> patch review ___ Python tracker ___

[issue8722] Documentation for __getattr__

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8722 ___ ___ Python-bugs-list

[issue8722] Documentation for __getattr__

Changes by David Stanek dsta...@dstanek.com: -- nosy: +dstanek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8722 ___ ___ Python-bugs-list mailing

[issue8722] Documentation for __getattr__

Terry J. Reedy tjre...@udel.edu added the comment: The problem with changing 2.7 docs is that object access is different for old- and new-style properties. Does your example work if you remove 'object'? (IE, can old style classes have properties?) For new-style classes, the example behavior

[issue8722] Documentation for __getattr__

Terry J. Reedy tjre...@udel.edu added the comment: /raise/raises/ I am pretty sure that when __getattribute__ is bypassed, so is __getattr__. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8722

[issue8722] Documentation for __getattr__

Éric Araujo mer...@netwok.org added the comment: Old-style classes can’t have descriptors, hence no properties, static methods, class methods or super. -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8722

[issue8722] Documentation for __getattr__

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8722 ___

[issue8722] Documentation for __getattr__

New submission from Paul Davis paul.joseph.da...@gmail.com: The docs for __getattr__ in the object model section could be more specific on the behavior when a @property raises an AttributeError and there is a custom __getattr__ defined. Specifically, it wasn't exactly clear that __getattr__

[issue8722] Documentation for __getattr__

Paul Davis paul.joseph.da...@gmail.com added the comment: I should mention, in example.py, it wasn't immediately clear that print f.bing would actually print instead of raising the AttributeError. As in, I had a property raising an unexpected error that happend to be an AttributeError. If its