Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Author
|
I signed my cla |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #705.
Do not emit an empty line when WrappedJoin's first item exceeds the available width. Existing wrapping and long tokens are preserved. Adds regression tests for single/multiple items and the availability-line alignment in help text.
Tests: 276 passed on Python 3.9 and 3.12; Python 3.12 was tested both with and without IPython. All changed files pass pylint.
The broader CI-style checks have existing baseline failures: pylint reports one ctypes-constructor diagnostic in formatting_windows.py; ty reports 23 diagnostics in unchanged modules. I reproduced the same diagnostics on clean upstream 716bbc2 with the same environment. This PR does not claim those checks are green.
AI assistance: Codex.