Marc-Andre Lemburg <m...@egenix.com> added the comment: Brian Curtin wrote: > > Brian Curtin <cur...@acm.org> added the comment: > > The previously mentioned comments about backwards incompatibility with the > number of items in the sequence are now a problem, since structseq now > inherits from tuple. It seems that n_in_sequence gets ignored and we have a 9 > item tuple.
But that's not a problem with this ticket, is it. The previous use case has to be restored (after all, this was the main reason for adding structseq years ago). Someone goofed when making the said change to structseq. Is there a ticket open for this ? Here's the change: http://svn.python.org/view?view=rev&revision=82636 After some digging: Looks like it's being dealt with on http://bugs.python.org/issue8413 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7766> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
