✅ Deploy Preview for python-cpython-preview ready!

Name	Link
🔨 Latest commit	d60b638
🔍 Latest deploy log	https://app.netlify.com/sites/python-cpython-preview/deploys/63918b34d3e53b0009a7191d
😎 Deploy Preview	https://deploy-preview-100103--python-cpython-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Looks like doctest does not support having both output and an exception in an example, but that's the entire point here: showing that the loop body is executed up to the point where the error condition (one iterable being exhausted) is hit. Any ideas?

You could try a try/except and print the exception instead (assuming it does work).

Yeah, I suppose that would work around it, but it'd also add significant noise to the example (five lines instead of two). :-/

For reference, this is the old open issue about doctest not supporting this: #65382. (Thanks, han-solo!) Looks like I have finally found a real-world stdlib use case for this feature. :-)

In that case, maybe just a comment above the line saying what it'll print (or the length) would work to be less noisy, though at that point the output wouldn't exactly match the display so also not too certain about that.

The only alternative I can think of is disabling the test for that example using # doctest: +SKIP, accompanied by a comment about that issue (not certain, but I think rST supports that).