> > What user code exactly would break? Would that be a serious problem? > > All code which assumes a tuple as return value. It's hard to > say how much code makes such an assumption. Most Python > code probably only uses the sequence interface, but the C interface > was deliberately designed to return tuples so that C programmers > can easily access the data. I believe that code would continue to work if you got a instance of a tuple subtype. > I don't see a need to argue over this. It's no use putting > a lot of work into inventing some overly complex (subclassing > types, etc.) strategy to maintain backwards compatibility > when an easy solution is so close at hand. Subclassing tuples is not at all overly complex. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4