Jack Jansen wrote: > Having to register the error handler first and then finding it by name > smells like a very big hack to me. I understand the reasoning (that you > don't want to modify the API of a gazillion C routines to add an error > object argument) but it still seems like a hack.... Well, in that case, you would have to call the whole codec registry a hack ;-) I find having the callback available by an alias name very user friendly, but YMMV. The main reason behind this way of doing it is to maintain C API compatibility without adding a complete new b/w compatiblity layer (Walter started out this way; see the SF patch page). -- Marc-Andre Lemburg CEO eGenix.com Software GmbH _______________________________________________________________________ eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/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