> I get the impression that I'm currently seeing a non-NULL third > argument in my (C) methods even though the method is called without > keyword arguments. > Is this new semantics that I missed the discussion about, or is this a bug? Can't tell without spending more time looking at the code and experimenting than I can afford today; but Jeremy refactored the calling code, and it could be that you're seeing an empty dictionary instead of a NULL. Do you really need the NULL? --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