Senthil Kumaran <orsent...@gmail.com> added the comment: On Fri, Nov 12, 2010 at 12:35:49AM +0000, Łukasz Langa wrote: > This is unfortunately a backwards compatibility concern. Originally > it wasn't made so that set() converts to string or accepts only > strings and when the developers realized this mistake, it was too > late (there were programs using this misfeature). That's one of the
Where would coercing to str() for set methods result in failures or backward compatibility problems? I think get() methods always return strings. ---------- nosy: +orsenthil _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10387> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
