setattr using invalid attribute names - bug or feature?
From: Gerson Kurz (gerson.kurz_at_t-online.de)
Date: 06/14/04
- Next message: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Previous message: Neale: "Re: Newbie array question"
- Next in thread: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Reply: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Reply: Meno: "Re: setattr using invalid attribute names - bug or feature?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 14 Jun 2004 14:22:17 GMT
I stumbled across this (while using my homebrewn enum class):
class test:
pass
instance = test()
setattr(instance, "THIS :*2+~# IS OBVIOUSLY INVALID", 123)
I would've expected some kind of error message here when calling
setattr(); after all, its not a regular attribute? Plus, documentation
says
"
Set a named attribute on an object; setattr(x, 'y', v) is equivalent
to
``x.y = v''.
"
and you cannot write this:
instance.THIS :*2+~# IS OBVIOUSLY INVALID = 123
(oh, and its: PythonWin 2.3.3 (#51, Dec 18 2003, 20:22:39) [MSC v.1200
32 bit (Intel)] on win32.)
- Next message: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Previous message: Neale: "Re: Newbie array question"
- Next in thread: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Reply: Peter Hansen: "Re: setattr using invalid attribute names - bug or feature?"
- Reply: Meno: "Re: setattr using invalid attribute names - bug or feature?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|