Antoine Pitrou added the comment: > When it comes to deferral, we could wrap each line in a different > class than tuple, but this constitutes a public API change (and this > is a *very* widely used library). Even changing to a namedtuple > would cause a lot of grief, since we'd break lots of doctests, and > subclassing tuple is a lot of effort for little benefit. If we only > do it for the deferred usage, it would "only" be inconsistent. I > suppose we could have a completely separate way of doing things for > ExceptionSummary, but again, inconsistent, and I think if one > extract_xxx method provides the functionality, users would expect it > to be available in the others.
YMMV, but I think we should go for inconsistency here. The other APIs in the traceback module are low-level and clearly limited by the type of objects they return. This feature request is a good opportunity to design something a little more future-proof. I'd love to know what other developers/contributors think here. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17911> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
