[issue2515] Segfault while operating on closed sqlite3 cursor.
New submission from Paul Davis <[EMAIL PROTECTED]>: Replicated on: #Ubuntu 7.0 Python 2.5.1 (r251:54863, Mar 7 2008, 03:39:23) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 #OS 10.4.11 Python 2.5.1 (r251:54863, Oct 26 2007, 16:52:32) [GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin #OS 10.5.2 Python 2.5.1 (r251:54863, Jan 17 2008, 19:35:17) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin -- components: Library (Lib) files: sqlite_segfault.py messages: 64753 nosy: pjdavis severity: normal status: open title: Segfault while operating on closed sqlite3 cursor. type: crash versions: Python 2.5 Added file: http://bugs.python.org/file9903/sqlite_segfault.py __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2515> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2515] Segfault while operating on closed sqlite3 cursor.
Paul Davis <[EMAIL PROTECTED]> added the comment: No prob. On Sun, Apr 6, 2008 at 7:06 AM, Gerhard Häring <[EMAIL PROTECTED]> wrote: > > Gerhard Häring <[EMAIL PROTECTED]> added the comment: > > Thanks for reporting this. It's fixed in r62183 in the 2.5 maintenance > branch. > > -- > resolution: -> fixed > status: open -> closed > > > > __ > Tracker <[EMAIL PROTECTED]> > <http://bugs.python.org/issue2515> > __ > __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2515> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8722] Documentation for __getattr__
New submission from Paul Davis : 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__ would be invoked after a @property was found and evaluated. The attached script demonstrates the issue on OS X 10.6, Python 2.6.1 I'm thinking something along the lines of: If the attribute search encounters an AttributeError (perhaps due to a @property raising the error) the search is considered a failure and __getattr__ is invoked. -- assignee: d...@python components: Documentation files: example.py messages: 105790 nosy: Paul.Davis, d...@python priority: normal severity: normal status: open title: Documentation for __getattr__ type: feature request versions: Python 2.6 Added file: http://bugs.python.org/file17349/example.py ___ Python tracker <http://bugs.python.org/issue8722> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8722] Documentation for __getattr__
Paul Davis 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 not an attribute error, the error is not swallowed. I can see the obvious argument for "AttributeError means not found", it just wasn't immediately obvious what was going on. -- ___ Python tracker <http://bugs.python.org/issue8722> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
