Delaney, Timothy (Tim) schrieb: > A change to the documented behaviour should require a __future__ > import for at least one version. That's even assuming that the change > is desireable (I don't believe so). We have multiple anecdotes of > actual, existing code that *will* break with this change. So far I > haven't seen any actual code posted that is currently broken by the > existing behaviour.
Can you please point to them? I'm only aware of a single anecdote (about software that likely will never see Python 2.6). Regards, Martin _______________________________________________ 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
