RetroSearch Browse

Wed Mar 14 23:08:34 CET 2007 · https://mail.python.org/pipermail/python-dev/2007-March/071954.html

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

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2007-March/071954.html below:

[Python-Dev] Proposal to revert r54204 (splitext change)