Skip to content

Add Python 3.7 support to Travis CI testing #584

Closed

Description

@roycaihw

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

Activity

  1. sellers commented on Jul 26, 2018

    @sellers

    see #558

  2. Lawouach commented on Aug 7, 2018

    @Lawouach

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

  3. eastlondoner commented on Nov 5, 2018

    @eastlondoner

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

  4. roycaihw commented on Nov 7, 2018

    @roycaihw
    MemberAuthor

    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

  5. changed the title [-]Add Python 3.7 support[/-] [+]Add Python 3.7 support to Travis CI testing[/+] on Nov 7, 2018
  6. fejta-bot commented on Apr 26, 2019

    @fejta-bot

    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

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2019
  8. fejta-bot commented on May 26, 2019

    @fejta-bot

    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

  9. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 26, 2019
  10. fejta-bot commented on Jun 25, 2019

    @fejta-bot

    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

  11. k8s-ci-robot commented on Jun 25, 2019

    @k8s-ci-robot
    Contributor

    @fejta-bot: Closing this issue.

    Details

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions