Bug #858016 shows how issubclass can segfault if you pass a deeply nested tuple as issubclass' second argument. I would like to propose changing the semantics so that it only accepts a flat tuple; when a tuple is passed in to do a quick check that each item is a class and if it is pass that to issubclass. But this is a change in semantics. Tim said I should clear it here first so that is what I am doing. Anyone have issues if I do this? And if so, any objections of backporting to 2.3? -Brett
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