On 16/03/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > What's *actually* under dispute here is whether it's acceptable to classify > this perfectly useful-as-is behavior, that was documented and tested in > released versions of Python for several years (with patches to change its > behavior explicitly rejected in the past), as a "bug".
Just to put this into context, the word "bug" is probably not the best to use here. The orignal behaviour was described as a bug, certainly, but that's not how the change has been treated. If the behaviour was being deemed a "bug", it would be acceptable in a "bugfix" release (ie. 2.5.1). No-one is advocating that. Rather, the change is being treated as a behaviour change (which it is) and submitted for a *feature* release (2.6). Whether the behaviour change is good, reasonable, acceptable - that's the question here. (And one on which I don't have an opinion!) Paul _______________________________________________ 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
