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

Add Python 3.7 support to Travis CI testing #584

Closed
1 task
roycaihw opened this issue Jul 25, 2018 · 8 comments
Closed
1 task

Add Python 3.7 support to Travis CI testing #584

roycaihw opened this issue Jul 25, 2018 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@roycaihw
Copy link
Member

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

@sellers
Copy link

sellers commented Jul 26, 2018

see #558

@Lawouach
Copy link

Lawouach commented Aug 7, 2018

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 :)

@eastlondoner
Copy link

I made a PR to update the client code in the 6.0 branch: #682

@roycaihw
Copy link
Member Author

roycaihw commented Nov 7, 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 roycaihw changed the title Add Python 3.7 support Add Python 3.7 support to Travis CI testing Nov 7, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 26, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 26, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants