A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-September/009280.html below:

[Python-Dev] PyObject_SetAttr/GetAttr() and non-string attribute names

[Python-Dev] PyObject_SetAttr/GetAttr() and non-string attribute names [Python-Dev] PyObject_SetAttr/GetAttr() and non-string attribute namesM.-A. Lemburg mal@lemburg.com
Fri, 08 Sep 2000 23:48:18 +0200
While hacking along on a patch to let set|get|hasattr() accept
Unicode attribute names, I found that all current tp_getattro
and tp_setattro implementations (classes, instances, methods) expect
to find string objects as argument and don't even check for this.

Is this documented somewhere ? Should we make the existing
implementations aware of other objects as well ? Should we
fix the de-facto definition to string attribute names ?

My current solution does the latter. It's available as patch
on SF.

-- 
Marc-Andre Lemburg
______________________________________________________________________
Business:                                      http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4