> I'm going with exc_clear(), since 'clearing' seems to be the verb > most people are using when talking about the action it performed. OK. > Implementation question: I'm planning to reuse the reset_exc_info function > defined statically in ceval.c. Which of these options do you prefer: > > 1) Just remove the static declaration from reset_exc_info and add the > prototype as an extern declaration to sysmodule.c. It has to be renamed to have a proper Py*** name too. > 2) Remove the static declaration from reset_exc_info and add the prototype > to an include file. If so, which include file is the most appropriate > place? ceval.h. > 3) Move the implementation of reset_exc_info out of ceval to another, more > public, file. If so, which one? I see no need. > I ask only because I usually submit bug fixes and minor changes, and am not > familar enough with this part of the Python development culture. Looks like you're catching on fast. :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
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