Bugs in CPython 3.1.1 [wave.py]
Alf P. Steinbach
alfps at start.no
Wed Jan 13 09:34:55 CET 2010
* Steven D'Aprano:
> Nobody is trying to understate the complexity of writing a large
> application that supports both 2.6 and 3.x, or of taking an existing
> library written for 2.5 and upgrading it to support 3.1. But the
> magnitude of these tasks is no greater (and potentially smaller) than
> supporting (say) 2.3 through 2.5. To describe it as "hopeless" is simply
> mistaken and weakens your credibility.
It seems that people here put a lot of meaning into "hopeless"...
Would it be better to say that it's "hard" or "very hard" or "impractical for
After all, the bug that this thread is about demonstrated that unit tests
designed for 2.x do not necessarily uncover 3.x incompatibilities.
Even at the level of Python's own standard library.
But, regarding reformulations that don't imply untrue things to anyone (or
nearly), I'd like the text on that page to still fit on one page. :-)
More information about the Python-list