On 3/16/07, "Martin v. Löwis" <[EMAIL PROTECTED]> 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. Mike _______________________________________________ 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
