Phillip J. Eby schrieb: > Some other options: > > 1. Deprecate splitext() and remove it in 3.0
How would that help the problem? Isn't it useful to have a function that strips off the extension? > 2. Add an optional flag argument to enable the new behavior How would that help backwards compatibility? > 3. Create a new function with the new behavior (as you proposed the last > time there was a patch submitted for this) What to do with the old function in this case? 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
