-
Notifications
You must be signed in to change notification settings - Fork 17
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
fix!: drop python 2.7 support #103
Conversation
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.
Generally looks good to me, just a few bits remaining - things from the comments and a few mentions of "Python 2" and "2.7" in the docs that are now obsolete, e.g in CONTRIBUTING.rst
and at the end of README.
@@ -12,4 +12,4 @@ | |||
# See the License for the specific language governing permissions and | |||
# limitations under the License. | |||
|
|||
__version__ = "1.7.0" | |||
__version__ = "2.0.0b1" |
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.
Same process question - should this be beta or an RC?
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.
As I said in googleapis/python-api-core#212, I think a beta is sensible for a semver-major breaking change. I'll let @crwilcox and @busunkim96 chime in on that.
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.
Also update the "Deprecated Python Versions" section in README like in other libraries?
Looks good otherwise, IMO.
Marked as |
@tseaver 12014e2 has not been pushed yet? I can still see references to Python 2.7 in CONTRIBUTING when I pull the PR branch locally. Edit: Ah, the owlbot commit overrode those changes. Was that added to the PR branch involuntarily? Edit 2 The CONTRIBUTING file is tempalted and must be modified through |
Release-As: 2.0.0b1 Closes #102
0862f04
to
85775cc
Compare
…oud-core into 102-drop-python-2.7
Except for the README section documentin the last version supporting it.
Ugh, OwlBot is restoring the |
🤖 I have created a release \*beep\* \*boop\* --- ## [2.0.0](https://www.github.com/googleapis/python-cloud-core/compare/v2.0.0-b1...v2.0.0) (2021-08-18) ### ⚠ BREAKING CHANGES * drop python 2.7 support ([#103](https://www.github.com/googleapis/python-cloud-core/issues/103)) ([181d706](https://www.github.com/googleapis/python-cloud-core/commit/181d706e5b44d9d4189c21782551ce85c720d733)), closes [#102](https://www.github.com/googleapis/python-cloud-core/issues/102) ### Miscellaneous Chores * trigger 2.0.0 release ([#128](https://www.github.com/googleapis/python-cloud-core/issues/128)) ([aead67a](https://www.github.com/googleapis/python-cloud-core/commit/aead67a1244306d518b8ab150e143e5a29e1ab6f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Release-As: 2.0.0b1
Closes #102.