-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 kafka-python deprecated? #2290
Comments
Damn, It would be painful. |
Im not doing new feature work currently. I am not aware of serious
compatibility issues, apart from new broker features that are not supported.
Bigger picture, there were 2 of us actively maintaining this project for
several years. Both have since moved to companies that do not use this
library. If there are others who are actively using and would like to join
the maintainer team, please reach out!
…On Mon, Jan 10, 2022, 8:26 AM Twy ***@***.***> wrote:
Damn, It would be painful.
—
Reply to this email directly, view it on GitHub
<#2290 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGN5NFKDQFUMUWEUUXUUULUVMCBZANCNFSM5LLCKSNA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Others are not able to get wheels for 3.10 out (https://github.com/confluentinc/confluent-kafka-python), so I really appreciate You keep up the work. I'll try and contribute if I can. I have a pretty complex ssl rig that triggers some bugs and hangs. |
Please, be honest and declare if this project is deprecated. I was building another project which uses the current committed code in the main branch. It's requirements install step pulled the latest released version 2.0.2, but then I was debugging 'Unrecognized configs: .... KafkaClient' messages for quite a while before I had the idea to check if the erroring code line, committed ~2 years ago, was in fact not part of the latest release. Is another package recommend in place of this one? |
Aiven is recommending the use of this package: https://docs.aiven.io/docs/products/kafka/howto/connect-with-python.html They should really put some resources into maintaining it. |
@dpkp Let me know if you're still in need of maintainers (email in profile). My company uses Kafka and Kafka-Python extensively and has need of some of the unreleased and in-PR functionality for this project, and so could surely come up with a maintainer or two. Alternately, have you considered moving this project to Jazzband? https://github.com/jazzband |
@hrichards your best bet is probably to directly email @dpkp (you can pull his email off one of his old commits). |
I reached out to @dpkp, if I don't hear back, I'm probably going to start working on building workflows in https://github.com/wbarnha/kafka-python-ng and automating creating pull requests from the existing ones here. |
Got push access, hopefully I'll get to revive this project shortly! |
Nearly done migrating the workflow to GitHub in #2378, this project should be coming back to life very soon. |
We're back! |
I'm still waiting on getting PyPi workflows ready, in case anyone revisits this. |
Refer to this for now: https://github.com/wbarnha/kafka-python-ng pip3 install kafka-python-ng |
No release in 1.5 yrs. Just wondering if eventually changes on Kafka broker will become incompatible with what we have. Is the project dead?
The text was updated successfully, but these errors were encountered: