Martin, Sorry you disagree. I think that the issue is still important and other pieces of the API are already in this direction. For instance, there is no need to have PyImport_AppendInittab because you can hack config.c (which you can get from $prefix/lib/pythonx.x/config/config.c) and in fact many people did exactly that but it made for a messy extension until the API call made it clean and direct. You don't need Py_AtExit() because you can call through to atexit.register() to put the function in. The list goes on... I still think that Py_AtInit() is clean, symmetric with Py_AtExit(), and solves a big problem for extenders who wish to address localization from within C (as opposed to sitecustomize.py). This is a 10 line patch with 0 runtime impact that requires no maintanence to move forward with new versions. If it were more than that, I could better understand your objections. Hope that I can get you to at least vote 0 instead of -1. Cheers, Pat -- Patrick Miller | (925) 423-0309 | http://www.llnl.gov/CASC/people/pmiller You can never solve a problem on the level on which it was created. -- Albert Einstein, physicist, Nobel laureate (1879-1955)
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