Fix pydoc doctest failures by updating expected output format for string operations #7703
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pyodide pipeline was failing due to doctest mismatches in the Z3 Python API. The issue was that Z3's string representation for sequence extraction operations changed from
Extract(...)format tostr.substr(...)format, but the docstring examples still expected the old format.Changes made:
Extractfunction: Updated expected output fromExtract(StringVal("hello"), 1, 3)tostr.substr("hello", 1, 3)SubStringfunction: Updated expected output fromExtract(StringVal("hello world"), 6, 5)tostr.substr("hello world", 6, 5)SubSeqfunction: Updated expected output fromExtract(StringVal("hello world"), 0, 5)tostr.substr("hello world", 0, 5)Example of the fix:
These changes align the documentation with Z3's current output format and resolve the build failures in the pyodide pipeline.
Fixes #7702.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.