I noticed that in Tkinter.py curselection() always
return strings instead of ints, (users have to use
map(int, list) to get the int values) but why? Here's
the code I found in Python 2.2/2.3. It seems someone
has noticed the problem before.

    def curselection(self):
        """Return list of indices of currently selected
item."""
        # XXX Ought to apply self._getints()...
        return self.tk.splitlist(self.tk.call(
            self._w, 'curselection'))
 
 

Indeed, it should call self._getints, not sure why it was never done.
Fixing this gives curselection the correct behavior according to the Tk
Reference Manual: http://tmml.sourceforge.net/doc/tk/listbox.html

Just a bare self._getints will raise an exception with no item selected
and an empty string returned, so I'm adding a patch to check for it and
return an empty tuple in that case, or the tuple with ints.

It's open for discussion if we should follow Tk documentation strictly
and return an empty string if no item selected, or keep consistency with
Python and other Tkinter parts and always return a tuple.

Not sure what you did, but calling _getints didn't raise an exception
here neither returned an empty string if no item was selected, it
returned None.

I used the tuple from splitlist() in both cases. I'm not sure if it
should return None on an empty selection since that is not documented
anywhere.

_getints already call splitlist, so there isn't much point in calling
_getints after calling splitlist.

And the Tk documentation says an empty string should be returned in case
there is no selection, but that is Tk. I don't see any problem in
returning None instead of '' here in Python.

Neither I do, but the current version already returns an empty tuple.
Since the map(int, curselection) idiom is widely used, changing to int
is not likely to break any code, but returning None on empty selection is.

Are you aware of any code checking against empty tuple specifically to
verify that nothing is selected ?

I found some code using map(int, curselection..) directly, so this new
patch fixes the problem related to returning None when nothing was selected.

Closing this in favour of issue6181 as it contains several other minor
fixes in Listbox that now have been tested in the
tk_and_idle_maintenance branch.