Patrick Maupin schrieb: > The worst part is, if they are relying on that specific behavior and have > to rely on the new specific behavior, and want to support old and new > versions of Python, they are potentially left with some very unattractive > options -- check the Python version to figure out how splitext works, or > just roll their own and stop calling splitext entirely, because its behavior > is not consistent across versions.
Somebody has pointed out that it is fairly easy to write a wrapper around splitext that explicitly produces the old behavior on all versions, or the new behavior on all versions, depending on what precisely is desired. Users that have coded for a specific behavior will have to write a wrapper - whether they explicitly code for the old behavior or the new one. 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