Python: Add Python 3.7 support to Travis CI testing

Created on 25 Jul 2018 · 8Comments · Source: kubernetes-client/python

Python 3.7 is released and we need to add it to our ci

[ ] Currently workaround exists but 3.7 isn't officially supported by travis ci: https://github.com/travis-ci/travis-ci/issues/9815

lifecyclrotten

Source

roycaihw

👍4

Most helpful comment

Hey folks,

Just a friendly ping to know the status of this one. Following #558, a fix was merged but I'm a little confused about what needs to be addressed still? Also, as this a breaking change (we have moved to Python 3.7 and currently can't use the kube client with it), is there a potential ETA by any chance? :)

Thanks :)

edit: I think I can just do pip install --pre --upgrade kubernetes for now :)

Lawouach on 7 Aug 2018

👍3

All 8 comments

see #558

sellers on 26 Jul 2018

Hey folks,

Thanks :)

edit: I think I can just do pip install --pre --upgrade kubernetes for now :)

Lawouach on 7 Aug 2018

👍3

I made a PR to update the client code in the 6.0 branch: https://github.com/kubernetes-client/python/pull/682

eastlondoner on 5 Nov 2018

This issue is about testing this client in Travis CI with Python 3.7. The client itself already resolved the reserved keyword conflict since 7.0.0a1 release: https://github.com/kubernetes-client/python/blob/master/CHANGELOG.md#v700a1

roycaihw on 7 Nov 2018

👍1

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 26 Apr 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 26 May 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 25 Jun 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.