>>Have you found any situation where this particular operation was >>time-critical? Each time a module's attribute is accessed with: from module import attr or module.attr a routine assigned to module tp->getattro is called (through PyObject_GetAttr, object.c,eval.c). Is it time-critical? As for small Python applications, no. However it probably could help in case of monsters like wxPython or Zope. (improving the applications startup performance as well). >>I believe (without thinking it through in detail) that the generic >>getattr/setattr routines are required in order to support subclassing >>of modules, which people use. Adding tp->tp_dict check->PyType_Ready-call to suggested new getattr/setattr routines wouldn't hurt much so subclassing could/will work, while "regular" modules could still benefit from suggested changes. >>So I think your suggestion cannot work, and I also think it is >>unnecessary, so I don't believe it is worth the bother. It works (tested). I wouldn't bother you otherwise. Well, all this is doable from a C extension module, so yes, modifying moduleobject.c is unnecessary. Sorry for taking your time. Regards, Wiktor http://www.wiktorsadowski.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