On Wed, Mar 4, 2009 at 17:30, Raymond Hettinger <pyt...@rcn.com> wrote:
> Just noticed that the empty() and full() methods were still there. >>> IIRC, we agreed to take them out (but leaving qsize() exposed). >>> The docs entries and test cases were taken out, but the actual >>> methods were accidentally left in. >>> >> >> If so, the only thing to do is deprecate it in 3.1 for removal in 3.2. >> > > I recommend adding a warning to 3.0.2 and removing in 3.1. > Waiting for more 3.x uptake doesn't serve our users well. > IIRC, that was the rationale for cmp() removal in 3.0.1. Right, but that's because 3.0.1 was released within four months of 3.0.0. Who knows when 3.0.2 will be released. Having some users suddenly get a new deprecation for some code just because they upgraded their interpreter doesn't sound very backwards-compatible to me. This is true even for a PendingDeprecationWarning. -1 on tossing a warning into 3.0.2 and going +1 with the 3.1 deprecation. -Brett
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
