[Python-Dev] Proposal to revert r54204 (splitext change) (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Fri Mar 16 13:31:20 CET 2007
- Previous message: [Python-Dev] Proposal to revert r54204 (splitext change)
- Next message: [Python-Dev] Proposal to revert r54204 (splitext change)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] Proposal to revert r54204 (splitext change)
- Next message: [Python-Dev] Proposal to revert r54204 (splitext change)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]