David W. Lambert added the comment: Sorry again. You probably didn't follow the link I posted to see the problem origination. Which was "Cannot subclass str." I generalized this to tuple.
On Tue, 2012-12-04 at 20:08 +0000, R. David Murray wrote: > R. David Murray added the comment: > > I have no idea what you are referring to by 'constructing str' :( > > I thought at first it was your incorrect tuple call in the init that was the > issue, but that didn't look right, and after reproducing it and playing with > it for a bit I figured out it was the __new__ failure, and I realized the > reason I was confused was that the error message said 'tuple' instead of 'c'. > So I definitely think that message could use improvement if it is practical. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue16608> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16608> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
