➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Nathaniel Manista
Recipients Nathaniel Manista, docs@python
Date 2018-09-12.20:03:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536782604.59.0.956365154283.issue34648@psf.upfronthosting.co.za>
In-reply-to
Content 
So I'm fixing a bug in typeshed's accounting of the traceback module (https://github.com/python/typeshed/pull/2436) and the documented semantics of traceback.format_list don't quite smell to me what I think they might be intended to be:

1) I know it has the name "format_list", but is it really intended to require a list? Why not a sequence, or a collection, or an iterable? I would think it would be fine to pass an iterable to traceback.format_list. Is it fine?

2) What is the desired component type for the aggregate passed to format_list? In 3.4-and-earlier it was Tuple[str, int, str, Optional[str]], and that still works in 3.5-through-3.8, but is that just backwards compatibility or is that something that users of traceback.format_list should feel encouraged to continue passing into the future?

Sorry for filing a bug just to ask "huh; really?" but... please confirm?
History
Date User Action Args
2018-09-12 20:03:24Nathaniel Manistasetrecipients: + Nathaniel Manista, docs@python
2018-09-12 20:03:24Nathaniel Manistasetmessageid: <1536782604.59.0.956365154283.issue34648@psf.upfronthosting.co.za>
2018-09-12 20:03:24Nathaniel Manistalinkissue34648 messages
2018-09-12 20:03:24Nathaniel Manistacreate