Skip to content

test: Rename python to python3 in tests #1223

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 1 commit into from
Mar 15, 2025

Conversation

dogukancagatay
Copy link
Contributor

This commit renames the invocation of python to python3 in the tests.

While many systems now alias python to python3, this behavior is not
guaranteed across all environments and is often configured by the user,
rather than provided by the operating system directly.

Explicitly using python3 ensures that the tests are executed with the
intended Python 3 interpreter, regardless of user-specific configurations,
and therefore improves the portability and reliability of the test suite.

This commit renames the invocation of `python` to `python3` in the tests.

While many systems now alias `python` to `python3`, this behavior is not
guaranteed across all environments and is often configured by the user,
rather than provided by the operating system directly.

Explicitly using `python3` ensures that the tests are executed with the
intended Python 3 interpreter, regardless of user-specific configurations,
and therefore improves the portability and reliability of the test suite.
@dbanty dbanty changed the title fix(tests): Rename python to python3 in tests test: Rename python to python3 in tests Mar 15, 2025
@dbanty dbanty added this pull request to the merge queue Mar 15, 2025
Merged via the queue into openapi-generators:main with commit f08682e Mar 15, 2025
22 checks passed
micha91 pushed a commit to micha91/openapi-python-client that referenced this pull request May 13, 2025
This commit renames the invocation of `python` to `python3` in the
tests.

While many systems now alias `python` to `python3`, this behavior is not
guaranteed across all environments and is often configured by the user,
rather than provided by the operating system directly.

Explicitly using `python3` ensures that the tests are executed with the
intended Python 3 interpreter, regardless of user-specific
configurations,
and therefore improves the portability and reliability of the test
suite.
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.

2 participants