"Martin v. Loewis" wrote: > > Guido van Rossum <guido@python.org> writes: > > > That's what I wanted, but now that you mention it I'm not sure if the > > warning module can currrently detect from which module a particular C > > API is called -- it'll probably put the blame on a particular line in > > the user's code, and then repeat the warning for each *different* line > > of user code. > > What *could* be done, of course, is to give the warning at most once. If that's possible, I'm +1 on generating a warning for the first usage of PyArg_NoArgs(). Would be nice to have the warning include the calling module name -- don't know whether that's possible, though (I have next to no experience with the warning framework). -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & 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