RetroSearch Browse

Thu Mar 15 21:24:25 CET 2007 · https://mail.python.org/pipermail/python-dev/2007-March/071994.html

"Phillip J. Eby" <pje at telecommunity.com> wrote in message 
news:5.1.1.6.0.20070315105608.02ba5f58 at sparrow.telecommunity.com...

> The process of having warnings at least ensures that I can *discover*
> whether my programs depend on some behavior that has changed - rather 
> than > having something that used to work and now doesn't.

I am not familiar with the warning system, but it seems plausible that one 
could add to the end of .splitext (before it returns) an optional warning 
something like

if not ext and base[0] == '.':
    warn("Before 2.6, this would have returned (%s,%s) instead of (%s,%s)" 
% (ext, base, base, ext))

where base and ext have the obvious contents.  Is this what you want?

Terry Jan Reedy

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

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

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