Skip to content
This repository was archived by the owner on Mar 13, 2022. It is now read-only.
This repository was archived by the owner on Mar 13, 2022. It is now read-only.

support for asyncio #27

Closed
Closed

Description

@tomplus

Hi guys.

Do you consider providing this client library with support for asyncio ?

Regards,
Tomasz Prus

Activity

  1. mbohlool commented on Aug 15, 2017

    @mbohlool
    Contributor

    asyncio would be nice. I can label this PR as help-needed so somebody pick it up. It would be better if you create your proposal as an issue in the main repo that hopefully will get more attraction.

  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Aug 15, 2017
  3. tomplus commented on Aug 15, 2017

    @tomplus
    MemberAuthor

    @mbohlool thanks. I'll add an issue in the main repo.

  4. tomplus commented on Jul 4, 2018

    @tomplus
    MemberAuthor

    @mbohlool I’ve prepared the new library kubernetes_asyncio which is based on this Python client, but uses the asyncio generator from swagger-codegen. Additional PR to gen repository is already merged.

    Do you think it's possible to migrate this new library to official kubernetes-clients' repo? How can I do that?

  5. fejta-bot commented on Apr 24, 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

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 24, 2019
  7. mitar commented on Apr 24, 2019

    @mitar
    Contributor

    /remove-lifecycle stale

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 24, 2019
  9. fejta-bot commented on Jul 23, 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

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 23, 2019
  11. mitar commented on Jul 23, 2019

    @mitar
    Contributor

    /remove-lifecycle stale

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 23, 2019
  13. fejta-bot commented on Oct 21, 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

  14. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 21, 2019
  15. mitar commented on Oct 21, 2019

    @mitar
    Contributor

    /remove-lifecycle stale

  16. 28 remaining items

  17. k8s-triage-robot commented on Aug 22, 2021

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  18. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 22, 2021
  19. remram44 commented on Aug 22, 2021

    @remram44

    /remove-lifecycle stale

  20. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 22, 2021
  21. k8s-triage-robot commented on Nov 20, 2021

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  22. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 20, 2021
  23. mitar commented on Nov 21, 2021

    @mitar
    Contributor

    /remove-lifecycle stale

  24. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 21, 2021
  25. k8s-triage-robot commented on Feb 19, 2022

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  26. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 19, 2022
  27. mitar commented on Feb 25, 2022

    @mitar
    Contributor

    /remove-lifecycle stale

  28. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 25, 2022
  29. roycaihw commented on Mar 13, 2022

    @roycaihw
    Member

    This repo has been merged into the main python repo. We are archiving this repo. Please open a new issue in the main repo. Thanks!

    /close

  30. k8s-ci-robot commented on Mar 13, 2022

    @k8s-ci-robot
    Contributor

    @roycaihw: Closing this issue.

    Details

    In response to this:

    This repo has been merged into the main python repo. We are archiving this repo. Please open a new issue in the main repo. Thanks!

    /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

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions