Open mgorny opened 1 year ago
I have reached out to the original author a long time ago but with no response. I forgot about PEP 541, thank you for bringing this to my attention. I will submit an application.
Edit: It seems after reading the requirements for reachability:
The user of the Package Index is solely responsible for being reachable by the Package Index maintainers for matters concerning projects that the user owns. In every case where contacting the user is necessary, the maintainers will try to do so at least three times, using the following means of contact:
the e-mail address on file in the user’s profile on the Package Index; the e-mail address listed in the Author field for a given project uploaded to the Index; and any e-mail addresses found in the given project’s documentation on the Index or on the listed Home Page.
The maintainers stop trying to reach the user after six weeks.
It seems I need to reach out to PyYoshi a few more times before the owner is considered "unreachable".
Thanks.
I'm not sure if you are actually supposed to do that, and not the person handling your request. After all, how can PyPI admins know that you've actually contacted them?
I think filing a bug on their GitHub would also be a good step, as that is publicly visible.
Thanks.
I'm not sure if you are actually supposed to do that, and not the person handling your request. After all, how can PyPI admins know that you've actually contacted them?
I would forward emails to PyPi admins as evidence.
I think filing a bug on their GitHub would also be a good step, as that is publicly visible.
Agreed, I don't like the idea of invoking PEP 541, but it seems that this project is in need of it. Opening up an issue in advance would be morally right.
Edit: Sorry, I'm tired. I misread maintainers
, assuming it referred to me, not the index maintainers. I'm still going to reach out again to show good faith.
Howdy! Are there any updates on this?
Barring that, is there a future where the top-level name of this package is changed to alleviate collisions? (Granted it is useful that you can install this in place of cchardet and magically make other packages that know nothing about it work, but it does make a lot of situations messy, as the OP noted.)
Sorry, there are no updates on this at the moment. I have not been able to allocate the time to work on this. :sweat:
Reached out to the original developer, haven't heard back.
Could we use GitHub actions to automate the release of this package to PyPI under a second, separate namespace? That way people who are experiencing conflicts over import cchardet
have the option to depend on / pip install faust-faust_cchardet
and use it as import faust_cchardet
? The primary namespace for this fork could still be cchardet
, but people could access it via the auto-sync'd auto-published second package name to avoid the namespace overlap if they need/want that.
Could we use GitHub actions to automate the release of this package to PyPI under a second, separate namespace? That way people who are experiencing conflicts over
import cchardet
have the option to depend on / pip installfaust-faust_cchardet
and use it asimport faust_cchardet
? The primary namespace for this fork could still becchardet
, but people could access it via the auto-sync'd auto-published second package name to avoid the namespace overlap if they need/want that. Incomplete GitHub Actions idea
Hi, sorry I've been away! I've bit off more than I could chew, I didn't expect this revival to become so important as a dependency. I'll file a PEP 541 request for cchardet
and kafka-python
since I've been meaning to hand off these projects to people who have more of a pertinent interest in them.
Since the original
cchardet
project is clearly no longer maintained
no longer true PyYoshi/cChardet had no pypi releases between 2020-10-27 and 2024-06-06
diff
cd $(mktemp -d)
git clone --depth=1 https://github.com/PyYoshi/cChardet
cd cChardet/
git remote add faust-cchardet https://github.com/faust-streaming/cChardet
git fetch faust-cchardet master
git rev-parse master
# fa74a8e43a2685767296f4cc5bc4594d28713ab1
git rev-parse faust-cchardet/master
# 3af7068fc6f04dc777531da021057bfbe75313b2
git diff --stat master faust-cchardet/master -- src/cchardet/
git diff master faust-cchardet/master -- src/cchardet/
git diff --stat
src/cchardet/__init__.py | 10 ++--------
src/cchardet/__main__.py | 4 ----
src/cchardet/_cchardet.pyx | 43 ++++++++-----------------------------------
src/cchardet/cli/__init__.py | 0
src/cchardet/cli/cchardetect.py | 40 ----------------------------------------
src/cchardet/version.py | 1 +
6 files changed, 11 insertions(+), 87 deletions(-)
Since the original
cchardet
project is clearly no longer maintained, have you tried contacting the original author to give you permissions to take the PyPI project? And if that failed, applying for PEP 541 name reuse?Creating a fork has the problem that some packages will now require
cchardet
and some will requirefaust-cchardet
, and both can't be installed simultaneously which causes major problems for distributions.