On Sun, Dec 7, 2008 at 5:38 AM, Steve Holden <steve at holdenweb.com> wrote: > A point release just to remove a function whose withdrawal has been > advertised as a 3.0 change hardly seems worth the substantial effort of > cutting a release. If cmp() shouldn't have been in 3.0 and was then > there's surely no problem about removing it later as promised: anyone > who uses it in 3.0 code shouldn't be. > > If it doesn't have to wait for a major release then is there any real > need to cut the minor release immediately? Well, since 2to3 doesn't remove cmp, and it actually works, it's likely that people will be accidentally depending on it in code converted from 2.x. In the past, where there was a discrepancy between docs and code, we've often ruled in favor of the code using arguments like "it always worked like this so we'll break working code if we change it now". There's clearly an argument of timeliness there, which is why we'd like to get this fixed ASAP. The alternative, which nobody likes, would be to keep it around, deprecate it in 3.1, and remove it in 3.2 or 3.3. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
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