On Wed, May 20, 2026 at 12:37:20AM +0800, Tianyu Chen wrote:
> > First of all, it's not clear from neither the package name, nor the
> > package description, that this is a Python library. Folks versed in the
> > Python ecosystem may recognize the asyncio name and make the connection
> > but perhaps it should be more explicit. I would suggest naming the
> > source package "python-aiokafka" and of course the binary package
> > python3-aiokafka (etc.). It'd be also great to mention Python somewhere
> > in the package description.
>
> Thanks! I didn't add the python- prefix because this package is part of
> aio-libs. src:aio{cache,ftp,mysql} dont have python- so I didn't prefix
> that. Retitled.
That's a fair point! I see a bunch of source packages named aio*
indeed. Plenty are also named python-aio*. I have a slight preference
for python-aio* for the reasons I stated, but given the precedent I'll
understand your decision either way!
> > Second, it's worth pointing out that Confluent's library, packaged in
> > Debian as python3-confluent-kafka, will support asyncio with the 2.13
> > release (not yet in Debian):
> > https://www.confluent.io/blog/confluent-kafka-clients-2-13-0-release-python-async/
> >
> > It would perhaps be nice to clarify the strengths of aiokafka over the
> > "official" implementation in the package description.
>
> Seems aiokafka's readthedocs have a page for the differences:
> https://aiokafka.readthedocs.io/en/stable/kafka-python_difference.html
Sadly this is comparing aiokafka not to confluent-kafka, but to a
_third_ implementation, kafka-python. Debian packages a fork of
kafka-python (i.e. technically yet another implementation), named
kafka-python-ng, as src:python-kafka. Part of the reason why I asked for
a comparison is exactly the fact that so many exist :) That's a
nice-to-have though, not something I would consider a blocker.
Regards,
Faidon
