Skip to content

api_checker: Drop support for Python 2 #40395

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

Merged
merged 2 commits into from
Apr 18, 2022
Merged

api_checker: Drop support for Python 2 #40395

merged 2 commits into from
Apr 18, 2022

Conversation

jorng
Copy link
Contributor

@jorng jorng commented Dec 3, 2021

This converts the utils/api_checker scripts to support Python 3 only. It removes all from __future__ imports, and switches any python shebangs to python3.

This is part of an ongoing effort to explicitly move to Python 3 and remove any implied support for Python 2.

@jorng jorng requested review from nkcsgexi and tbkka December 3, 2021 18:59
@jorng
Copy link
Contributor Author

jorng commented Dec 3, 2021

@swift-ci please smoke test

@jorng jorng requested a review from edymtt December 3, 2021 19:05
This converts the `utils/api_checker` scripts to support Python 3 only.
It removes all `from __future__` imports, and switches any `python`
shebangs to `python3`.
@jorng
Copy link
Contributor Author

jorng commented Mar 9, 2022

@swift-ci please smoke test

@edymtt
Copy link
Contributor

edymtt commented Apr 18, 2022

@swift-ci please smoke test

@edymtt
Copy link
Contributor

edymtt commented Apr 18, 2022

cc @dduan -- using this PR to address one script that #42086 did not cover

Copy link
Contributor

@dduan dduan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@jorng jorng merged commit 7ec146b into swiftlang:main Apr 18, 2022
@jorng jorng deleted the api_checker-py3 branch April 18, 2022 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants