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.
pick leftmost version-shaped token in _parse_tool_version #778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
pick leftmost version-shaped token in _parse_tool_version #778
Changes from all commits
232b8c5File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "leftmost version-shaped token wins" heuristic only fails safe for black by coincidence: a leading
Python 3.xbanner is always< 22.3.0(black's CalVer), so it correctly lands on "NOT supported". Since this file is the shared vscode-python-tools template and the helper is generically named_parse_tool_version, copying it to a tool whose real version is in the 2.x/3.x range (e.g. isort/autopep8) would mistake a leading Python banner for a supported version. Consider anchoring selection onTOOL_MODULE, or at least add a comment noting the leftmost rule is only safe here because black's version numbers exceed CPython's.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bundled/is the shipped VSIX payload. Please confirm.vscodeignoreexcludesbundled/**/tests/**(or relocate these tests to the conventionalsrc/test/python_tests/location) so test code isn't shipped in the extension.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR headline is that a trailing
)(e.g.3.12.0)) is no longer swallowed, but in every test the returned leftmost token is followed by whitespace, so the)-stripping only ever affects the non-returned second candidate. Add a case that pins the headline behavior on the returned token, e.g.assert _parse_tool_version("black, 22.3.0)") == "22.3.0"(and ideally the no-space"black,22.3.0)"form).