Skip to content
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

updating version check to 3.12 #1813

Merged

Conversation

sameer-google
Copy link
Collaborator

@sameer-google sameer-google commented Oct 21, 2024

This PR updates the Python version compatibility for gsutil to support Python 3.8 through 3.12, while dropping support for older versions (3.5, 3.6, and 3.7). The following changes have been made:

  • Updated version check in gsutil.py to 3.8-3.12.
  • Updated the python_requires and classifiers in setup.py to specify compatibility with Python versions 3.8 to 3.12, removing references to unsupported versions (3.5, 3.6, and 3.7).

These updates align the project with the ongoing effort to support the latest Python versions while ensuring compatibility across all tested platforms.

@sushantkhanna
Copy link
Member

sushantkhanna commented Nov 25, 2024

Please squash the commits so that only a single commit gets merged into primary branch related to this change.
Please update the description.

@@ -126,16 +126,16 @@ def make_release_tree(self, base_dir, files):
'Natural Language :: English',
'Programming Language :: Python',
'Programming Language :: Python :: 3',
Copy link
Member

Choose a reason for hiding this comment

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

Even this line needs to be removed ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's useful for searchability on package indexes like PyPI, as some users may filter for projects compatible with Python 3 broadly, without specifying a minor version. We should only remove this line if the project does not support all minor versions of Python 3. Correct me if i am wrong.

Copy link
Member

Choose a reason for hiding this comment

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

Correct me if i am wrong. - I do not know the correct approach here, hence I had asked.
I think it's fine to have this as long as it does not specify that we are compatible with Python 3.0 ? Because we are not anymore.
Is there a way to simulate and verify this ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

As we are updating python_requires='>=3.8, <=3.12', this ensures that we are compatible only with 3.8 to 3.12.

we can keep the 'Programming Language :: Python :: 3' line, as long as we are not claiming compatibility with all versions of Python 3 (which could lead to confusion). IMO, It's fine to leave it, especially if we later specify the exact minor versions (e.g., Programming Language :: Python :: 3.8, Programming Language :: Python :: 3.12) as well.

@sameer-google
Copy link
Collaborator Author

Please squash the commits so that only a single commit gets merged into primary branch related to this change. Please update the description.

Squashed the commits and Updated PR description.

@sameer-google
Copy link
Collaborator Author

The kokoro tests failing in this PR are failing in the previous ones' as well.
The CI / build failures are due to a change in version check. These are resolved by CI build PR, merging alongside this PR.

@sushantkhanna sushantkhanna merged commit f7b016e into GoogleCloudPlatform:master Nov 26, 2024
21 of 36 checks passed
@sameer-google sameer-google deleted the update-version-check branch November 28, 2024 08:56
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