MAINTAINER NOTICE: RELEASES ARE CURRENTLY PAUSED HERE, VISIT THE FORK

[wbarnha]

Hi everyone,

Due to some complications with transferring PyPi credentials, I am unable to update the kafka-python namespace on PyPi. As a consequence, I have created a fork at https://github.com/wbarnha/kafka-python-ng. I will try to write a bot to transfer all existing PRs and Issues to the repository. For now, you can install the new project via:

pip3 install kafka-python-ng

I apologize that it took so long to make this decision.

[wbarnha]

I've been away for a while taking care of personal issues. In the meantime, I've been trying to get the old kafka-python system working again by migrating to kafka-python-ng. Maybe someone will find this useful someday. I transferred all issues from kafka-python to kafka-python-ng via some notes in https://jloh.co/posts/bulk-migrate-issues-github-cli/

gh issue list -s all --json number |     jq -r '.[] | .number' |     xargs -I% gh issue transfer % https://github.com/wbarnha/kafka-python-ng

Unfortunately, this only works if you're the owner of the project, which in this case for kafka-python, I am not. 😩
So I figured I could output all open issues from CLI via:

gh issue list -L 5000 -s all --json number |     jq -r '.[] | .number' |     xargs -I% gh issue view %

Pipe to a gh issue create:

gh issue list -R https://github.com/dpkp/kafka-python -L 5000 -s open --json number |     jq -r '.[] | .number' |     xargs -I% gh issue view % -R https://github.com/dpkp/kafka-python | 

(I ran this in a separate directory btw, hence -R), but doing it on a command line was painful so I wrote a script:

#!/bin/bash

remote_repo=https://github.com/dpkp/kafka-python
current_repo=https://github.com/wbarnha/kafka-python-ng
issue_limit=1

for issue_number in $(gh issue list -R $remote_repo -L $issue_limit -s open --json number |     jq -r '.[] | .number')
do
        issue_body=$(gh issue view $issue_number -R $remote_repo --json=body | jq -r '.body')
        issue_title=$(gh issue view $issue_number -R $remote_repo --json=title | jq -r '.title')
        echo "${issue_title}"
        echo "${issue_body}"
        gh issue create --title "${issue_title}" --body "${issue_body}" -R $current_repo
done

And for migrating PRs, I wrote this script:

#!/bin/bash

remote_repo=https://github.com/dpkp/kafka-python
current_repo=https://github.com/wbarnha/kafka-python-ng
issue_limit=5000

for issue_number in $(gh issue list -R $remote_repo -L $issue_limit -s open --json number |     jq -r '.[] | .number')
do
        if [ $issue_number  -lt 2391 ]
        then
                issue_body=$(gh issue view $issue_number -R $remote_repo --json=body | jq -r '.body')
                issue_title=$(gh issue view $issue_number -R $remote_repo --json=title | jq -r '.title')
                echo "${issue_title}"
                echo "${issue_body}"
                gh issue create --title "${issue_title}" --body "${issue_body}" -R $current_repo
                sleep 1s
        fi
done

I saw some errors like:

pull request create failed: GraphQL: Head sha can't be blank, Base sha can't be blank, Head repository can't be blank, No commits between wbarnha:master and jeffwidman:cleanup-max-bytes-tests, Head ref must be a branch, not all refs are readable (createPullRequest)

while attempting to open some PRs but didn't look into it further since the majority of PRs got pulled in and I can just do the remainder manually if need-be.

Hopefully this helps somebody else, someday.

[P1ng-W1n]

Hi @wbarnha

Sorry for asking this in the first place (I know, I have trust issues), but has there been any official announcement about the maintainer change? I was trying to find any reference that would indicate that @dpkp handed over the project maintenance to someone else, but ended up empty handed.
As this post is suggesting to use another repository / python package, so I think it would be good to communicate this clearly, otherwise people might have questions about the legitimacy of this request (considering the recent xz debacle) .

[wbarnha]

Hi there! It's a fair question. Dana has been wanting to get back to maintaining this project but has been busy with other affairs. I've been less active as well unfortunately since I'm currently in the process of getting my flame back.

As for the fork, I'm the one who maintains kafka-python-ng and I'll review PRs if pinged. If there are any that have been opened which I forgot about, please ping me!

[ssbarnea]

Another reason to worry is the fact that the project is not hosted under an github organization instead of a personal account. From the long term maintenance point of view, that is another liability similar to the one with pypi publishing. Hopefully this can be addressed.

PS. There are lots of github orgs designed to help with python project maintenance, which also makes it easier as others with experience can step in to help.

[maallaire]

Found the context of the "complications with transferring PyPi credentials" for those interested. pypi/support#3785 (comment)