RetroSearch Browse

Fri Mar 16 14:00:30 CET 2007 · https://mail.python.org/pipermail/python-dev/2007-March/072039.html

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

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

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

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