This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author W deW
Recipients W deW, docs@python, eryksun, martin.panter, vstinner
Date 2015-09-22.17:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442943533.45.0.708595790602.issue25205@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the ref to issue14029. I think I see how it works. As long as the object's __dict__ accepts the attributeName as a key, it needs not be a valid string nor a string at all. Though the latter *is* checked for, and that in turn can be circumvented by adding the attribute to the __dict__ directly. An object can be made attribute to itself.

However, the documentation falls short here. So far, I haven't found where it defines "attribute". Is there any point in defining an attribute that cannot be addressed as an attribute if the parser doesn't allow it?

It seems to me that in order to catch programing errors early, the default behaviour should include checking the valid syntax of the attribute's name.
History
Date User Action Args
2015-09-22 17:38:53W deWsetrecipients: + W deW, vstinner, docs@python, martin.panter, eryksun
2015-09-22 17:38:53W deWsetmessageid: <1442943533.45.0.708595790602.issue25205@psf.upfronthosting.co.za>
2015-09-22 17:38:53W deWlinkissue25205 messages
2015-09-22 17:38:53W deWcreate