deps: support Pythons <4

[cpcloud]

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1412 🦕

[cpcloud]

cc @tswast

[tswast]

@cpcloud I'm looking into this. It would be a departure from most of the other Google client libraries. Would you mind sharing some of the reasoning here why it's important to have a wider upper bound?

I assume partially it's so it's easier to test with prerelease versions of Python?

[cpcloud]

@tswast The main reason is for testing new Python versions not necessarily pre-release only though, since 3.11 has been out for about a month.

[cpcloud]

Should I put fix: prefix so that a release will be cut?

[cpcloud]

Seems the CLA check is failing, but I have signed one according to the link.

[chalmerlowe]

@cpcloud
Regarding the CLA check:

GH associated my gmail account with the change and NOT my google account and despite being a Googler and having my google address associated with my GH account, the CLA check only sees that [email protected] made the suggested change and co-authored a minor tweak. I am looking into how to reset the author on that change I suggested so that we can get past the CLA problem.
Sigh.

I attempted to reset the author using git on my local machine and push that change to GH, but it might have been pushed to your GH repo due to the various convolutions involved in pull requests, etc.

Sigh.

[cpcloud]

@chalmerlowe I went ahead and squashed it down to just myself as the author.

[chalmerlowe]

@chalmerlowe I went ahead and squashed it down to just myself as the author.

sweet. thanks.
once the tests pass, I will merge the change.

[tswast]

Should I put fix: prefix so that a release will be cut?

I think that'd be appropriate. I recall that deps will also show up in the changelog, so should also trigger a release.

[chalmerlowe]

LGTM

[cpcloud]

Thanks y'all!

[kevinfgordon]

@cpcloud thank you for this adjustment, I ran into the same issue trying to leverage this with 3.11 today. Eagerly awaiting the release to be completed.
FYI: The readme still references < 3.11 incase that should be adjusted to reflect the new change.