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

Phillip J. Eby pje at telecommunity.com
Fri Mar 16 02:39:23 CET 2007

At 10:39 PM 3/15/2007 +0100, Martin v. Löwis wrote:
>That said, if it makes people more comfortable with having a warning
>added, I won't object. It's just that I don't want to be the one to
>take the blame for issuing the warning, because deep in my heart I
>feel that warnings are a bad thing, unless they are right most of the
>time (which they won't be in this case).

Some other options:

1. Deprecate splitext() and remove it in 3.0

2. Add an optional flag argument to enable the new behavior

3. Create a new function with the new behavior (as you proposed the last 
time there was a patch submitted for this)

More information about the Python-Dev mailing list