New submission from nother :
Not sure where to file this suggestion properly and how.
Currently when mixing attributes and properties it can happen that an
AttributeError not raised intentionally by @property getter can cause @property
to vanish from from classinstance. This happens when on
nother added the comment:
Ah sorry, sure. Attached some examples hope they are not too artificially
simple to still render real world scenarios.
The one loaded was just the test that a function called from within the except
block inside another method can use raise keyword to reraise
nother added the comment:
The first two exampel should produce the same result not throwing any
exception. The third example should as it does report that prop is not
available for instance.
The fourth example should pass on the AttributeError raised for the not
available attr2 instead of
