Skip to content
This repository has been archived by the owner on Apr 2, 2023. It is now read-only.

Moving python client to its own repo #2

Closed
ridv opened this issue Feb 18, 2020 · 1 comment
Closed

Moving python client to its own repo #2

ridv opened this issue Feb 18, 2020 · 1 comment
Assignees
Milestone

Comments

@ridv
Copy link
Contributor

ridv commented Feb 18, 2020

As mentioned on the Aurora slack channel a few days ago, I'm currently ill equipped in terms of bandwidth and knowledge to maintain the Aurora python client.

Coupled with the fact that Python 2 will no longer be seeing security updates, I feel it's the right time to move the python client to its own repository. Hopefully, this opens up the opportunity for someone else to take over maintenance on their own schedule and bring it to Python 3.

I will do my best to simultaneously contribute new features and or changes necessary to allow the aurora python client to maintain compatibility with the later versions of the scheduler.

@ridv ridv self-assigned this Feb 18, 2020
@ridv
Copy link
Contributor Author

ridv commented Jul 28, 2020

Done in #10

@ridv ridv closed this as completed Jul 28, 2020
@ridv ridv added this to the 0.23.0 milestone Jul 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant