Guido: > - The mapping between the next() method and the tp_iternext slot in > the type object would disappear, and instead the __next__() method > would be mapped to this slot. For what it's worth, I took it upon myself to "fix" this already in Pyrex extension types. So if you make this change, you'll be making Python more compatible with Pyrex. :-) Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg@cosc.canterbury.ac.nz +--------------------------------------+
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