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

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 16, 2007, at 3:30 PM, Mike Krell wrote:

> On 3/16/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>
>> If they pass the flag to the function, the code will stop running on
>> 2.5 and earlier. This is worse than having code that works on all
>> versions. This is also whz I wondered how the flag helps backwards
>> compatibility: when people add the flag, the code stops working
>> on old versions, so it will *not* be backwards compatible.
>
> I don't understand.  Under Nick's proposal, calling splitext with no
> keyword parameters results in the exact behavior we have today, so
> it's obviously backward compatible.  If you use a keyword parameter,
> you're using a new feature implemented in 2.6, so there is no
> expectation of backward compatibility unless and until the keyword
> parameters are backported.

Let's remember the lessons of True and False in Python 2.2.1.

- -Barry


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRfr04nEjvBPtnXfVAQKxXgP9GmIx6OANec+aGsT9X9KoJsWLM+RGYrjB
RuDy5uxIbxfZg0logFzvTH4iLCnjJzfhhFrc8V9RjDf7I8vubM+caaEvZBDRoabW
bNO6L4IA1zGKjmKYhVhnLkRFNk3iEHwvG9Fa4ahqcCaeS99IYBejwtZ0Sqd171dL
ZQnUFBT5vBU=
=NlKx
-----END PGP SIGNATURE-----