>> self.assertRaises(ValueError, range, 1e100, 1e101, 1e101) > ... > Given this, there's approximately no chance gc *caused* it. Who's been > mucking with function calls (or maybe the eval loop) recently? It appears to be a refcount error in recently-added C code that tries to generalize the builtin range() function, specifically here: Fail: Py_XDECREF(curnum); Py_XDECREF(istep); <- here Py_XDECREF(zero); Word to the wise: don't ever try to reuse a variable whose address is passed to PyArg_ParseTuple for anything other than holding what PyArg_ParseTuple does or doesn't store into it. You'll never get the decrefs straight (and even if you manage to at first, the next person to modify your code will break it). only-consumed-eight-hours-this-time<wink>-ly y'rs - tim
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