-
Notifications
You must be signed in to change notification settings - Fork 41
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
Is this project still alive? #73
Comments
Hey, I'm no longer using this project. I think I would be happy to hand this over to any person who seems to have a trustworthy track record in OSS (not any volunteer since this package is depended upon by quite a few people) |
Hi, I am a celery core team member, we use this in celery if you add me to maintain this project I can keep it updated & released for the sake of compatibility with celery & airflow. |
@auvipy added ping me for release though, I will add you later to PyPI but I wanna take a quick look at things you merged before the next big release after such a long time. |
ok sure |
@auvipy heads up, if you are a maintainer now, this will stop working when Click 8 is released (in a few weeks) because the shell completion system was rewritten. Celery currently depends on Click < 8, but Flask 2 will depend on Click >= 8, so anyone using Flask with Celery will not be able to upgrade until Celery updates their pin, which they can't unless they drop this dependency or it gets updated. cc @ThiefMaster |
Yup some big overhaull needed |
I need some details on click changes that need to be worked on to make it v8.0 compatible |
@auvipy I'm not familiar with click-repl, so I'm not exactly sure what might be needed. However, the only thing that significantly changed in an incompatible way was the shell completion system. Commands, groups, parameters, and types all have |
@auvipy Hey, this is great. Thanks! |
we have a new release. @untitaker it would be a very helpful if i get acess to other packages like click-didyoumean & |
I am closing this since the project is alive now with new release. |
@auvipy those packages have their own maintainers respectively, if you want to have access on them please create a new issue there respectively. I can take care of the details if the respective maintainer agrees. |
ok |
Sorry for asking so directly, but the last release was in 10/2018, and since then none of the PRs that had been provided have been answered to or merged.
The text was updated successfully, but these errors were encountered: