Ralf W. Grosse-Kunstleve wrote: > http://docs.python.org/dev/whatsnew/ports.html says: > > The PyRange_New() function was removed. It was never documented, never used > in the core code, and had dangerously lax error checking. > > I use this function (don't remember how I found it; this was years ago), > therefore my code doesn't compile with 2.5b1 (it did OK before with 2.5a2). Is > there an alternative spelling for PyRange_New()? You can call PyRange_Type with the appropriate parameters. Georg
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