Catching errors in attribute names at assigment

[Thomas Philips]

If one makes a typographical error when assigning a value to an
attribute (i.e if one types ClassName.xyc = 10 instead of
ClassName.xyz=10), a new attribute xyc will be created, and the error
can later prove difficult to debug.

Is there a way to check assignments when they are made and to allow
only those that modify a restricted set of allowable attributes?
Looking through ClassName.__dict__.keys() is perhaps one way to
achieve this: Is there a simpler (i.e. more Pythonic) way to do it as
well?

Thomas Philips

[Pawel Kraszewski]

Thomas Philips wrote:

If one makes a typographical error when assigning a value to an
attribute (i.e if one types ClassName.xyc = 10 instead of
ClassName.xyz=10), a new attribute xyc will be created, and the error
can later prove difficult to debug. Is there a way to check assignments when they are made and to allow
only those that modify a restricted set of allowable attributes?
Looking through ClassName.__dict__.keys() is perhaps one way to
achieve this: Is there a simpler (i.e. more Pythonic) way to do it as
well?

Yes, there are at least two ways

The "new" way is to use "new classes" - ones being children of "object"
class - where you have a special attribute __all__ .

If you say __all__=["a","b","c"], those 3 attributes are the only ones valid
for field/method accessing. So class.a=5 is ok, but class.d=5 raises
exception.

The "old" way is to override __getattr__ and __setattr__ and check for a
valid name before accessing.

--
Pawel Kraszewski FreeBSD/Linux

E-Mail/Jabber Phone ICQ GG
Pa**************@wp.pl [phone] 45615564 69381

[Heather Coppersmith]

On Mon, 21 Jun 2004 22:01:31 +0200,
Pawel Kraszewski <pa**************@wp.pl> wrote:

If you say __all__=["a","b","c"], those 3 attributes are the
only ones valid for field/method accessing. So class.a=5 is ok,
but class.d=5 raises exception.

ITYM __slots__ instead of __all__.

Regards,
Heather

--
Heather Coppersmith
That's not right; that's not even wrong. -- Wolfgang Pauli

[Pawel Kraszewski]

Heather Coppersmith wrote:

If you say __all__=["a","b","c"], those 3 attributes are the
only ones valid for field/method accessing. So class.a=5 is ok,
but class.d=5 raises exception.

ITYM __slots__ instead of __all__.

My fault, __all__ is for module members, not class members.

Sorry for that.

--
Pawel Kraszewski FreeBSD/Linux

E-Mail/Jabber Phone ICQ GG
Pa**************@wp.pl [phone] 45615564 69381

[Duncan Booth]

tk****@hotmail.com (Thomas Philips) wrote in
news:b4*************************@posting.google.co m:

Is there a way to check assignments when they are made and to allow
only those that modify a restricted set of allowable attributes?
Looking through ClassName.__dict__.keys() is perhaps one way to
achieve this: Is there a simpler (i.e. more Pythonic) way to do it as
well?

Two more Pythonic ways to do this:

Write lots of unit tests. That way you not only catch this specific problem
but lots of others as well.

Use PyChecker. That way you not only catch this specific problem but lots
of others as well.