Guido wrote: > I'd be *very* surprised that a "mere" 10K lines of extension code > would require significant work to keep it working under 2.2. I don't > know where you get this idea, but Python's C API is actually quite > stable, and more often than not, no changes are necessary to keep > 1.5.2 code conformant with 2.2, or the changes are limited to 1 or 2 > lines per file. fwiw, I cannot recall ever having to change anything on the C API level when upgrading (and we're talking 100k's of lines here, starting at Python 1.2) downgrading is a different story (we generally support everything from 1.5.2 and upwards), but it usually only takes an #if PY_VERSION_HEX or two to fix that. </F>
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