On Wed, May 15, 2013 at 12:15 PM, dieter die...@handshake.de wrote:
If Python would automatically redecorate overridden methods in a derived
class, I would have no control over the process. What if I need
the undecorated method or a differently decorated method (an
uncached or
Sorry for digging this old topic back. I see that my 'property' does not
play well with polymorphic code comment generated some controversy. So
here's something in my defense:
Here's the link to stackoveflow topic I am talking about:
I seem to stumble upon a situation where != operator misbehaves in
python2.x. Not sure if it's my misunderstanding or a bug in python
implementation. Here's a demo code to reproduce the behavior -
# -*- coding: utf-8 -*-
from __future__ import unicode_literals, print_function
class
Thanks for clearing up. Developers of python should address this issue, in
my opinion. 3.4/3.5 maybe, but better late than never.
Recently, I've been beaten back for using some exotic features of python.
One is this[ Took me hours to get to the bottom ]. The other one is
'property' decorator. I
Is there any way to raise the original exception that made the call to
__getattr__? I seem to stumble upon a problem where multi-layered attribute
failure gets obscured due to use of __getattr__. Here's a dummy code to
demonstrate my problems:
import traceback
class BackupAlphabet(object):
