Failed to Build on Python 3.11.0 #81
Comments
|
Same here. |
|
nvm that issue mention, i made a little mistake and assumed that orjson depends on this, which it doesnt. |
|
Same here. |
|
Same here |
|
I encounter the same issue with the I have noticed it as I wanted to install aiohttp
cchardetFor the |
|
@PyYoshi Doesnt seem to come back to take care of this. Tried to contact them on all platforms I could find them on, never got any response. Its also well known that they don't maintain this, it has been like this for literal years. So chances for an update are very slim. I recommend everyone who uses this, to find an alternative. |
|
It is definitely a bit weird that the requirements mention However, I think one would have to also change other requirements, notably the version of Cython. |
|
Someone should fork this repo and start publishing it on Pypi as cchardet2.
Sep Dehpour
… On Nov 19, 2022, at 6:52 AM, Wok ***@***.***> wrote:
It is definitely a bit weird that the requirements mention chardet v3 when the current version is v5, which was updated for Python v3.11.
However, I think one would have to also change other requirements, notably the version of Cython.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
|
@seperman There is also a process that allows to transfer Pypi projects to a new user when the old owner is inactive. Don't know exactly how it works, but I know it exists |
|
That process needs it to go through some pypi committee voting to change ownership. I recently lost my 2 factor auth to pypi. In order to get back access to my account, Pypi took about eight months. It didn't even need to go through a committee, and it took that long.
Sep Dehpour
… On Nov 19, 2022, at 11:11 AM, ToasterUwU ***@***.***> wrote:
@seperman There is also a process that allows to transfer Pypi projects to a new user when the old owner is inactive.
Don't know exactly how it works, but I know it exists
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
Even if it takes long, it should still be done. Throwing it away and making a new package is not a good idea in my opinion. Since it forces everyone who depends on it to figure out there is a new one and than switch. |
|
Do you want to wait a couple of years until the PyPI committee votes for it? You can start the process now but in the meantime, have cchardet2 on pypi. Personally if I can not use it with Python 3.11 by the end of the month, I will simply stop using cchardet altogether.
Sep Dehpour
… On Nov 20, 2022, at 1:00 AM, ToasterUwU ***@***.***> wrote:
Even if it takes long, it should still be done.
Throwing it away and making a new package is not a good idea in my opinion. Since it forces everyone who depends on it to figure out there is a new one and than switch.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
@seperman Im neither attached enough to take this project under my wings, or enough of a C nerd to even be able to maintain this. Besides that, Pypi will not take years to do this. Definetly not. Multiple months is still quiet some time. But just slapping a 2 behind the name and than having the normal one still exist and look like the better option on first glance is not a better option than waiting. I agree there should be a new package for the meantime. But its crucial that the package with the most trustworthy name and most downloads and all that, is taken over as soon as its possible. |
|
We use this project for https://github.com/faust-streaming/faust and we're trying to migrate everything to support Python 3.11. I am willing to take a try at upgrading things in this project, in my own fork, for Python 3.11. |
|
@wbarnha Cool. Please let us know once you fork it. |
|
@ToasterUwU The last time @PyYoshi RIP pushed any code to this code base seems to be 2 years ago. |
|
I've made a fork at https://github.com/faust-streaming/cChardet and I'm going to merge the pending PRs into it. |
|
@seperman wheels for cchardet on Python 3.11 are now available! pip install faust-cchardetSadly, wheels for Windows are not available at the moment until I figure out what's going on with https://github.com/faust-streaming/cChardet/actions/runs/3568007197. Edit: I made a mistake and forgot to build Python 3.11 wheels. Should be fixed momentarily. |
|
Awesome! Thanks. |
|
@wbarnha thanks for taking this on, can you open issues on your fork? I'm encountering various problems, such as when installing via a setup.py And when installing manually: OS is Linux (Fedora 36), python version 3.10.8 |
|
I created an issues tab in my fork, sorry it wasn't already there. I'll take a look when I get the opportunity. |
|
Thanks a bunch @wbarnha , and yeah I think by default github doesn't create an issues tab on new repos, no reason to be sorry :) I'll file the two issues later today. |
`cchardet` hasn't had a commit in almost two years (8 days shy as of this commit). [This issue](PyYoshi/cChardet#81) is a six month old bug showing that `cchardet` doesn't support python 3.11, which is the most recent python. `cchardet` is fast, certainly, though the usage here is not as performance sensitive as would warrant its use over `chardet`, e.g. a difference of 800ms is probably not something that is worth keeping problematic dependencies around.
`cchardet` hasn't had a commit in almost two years (8 days shy as of this commit). [This issue](PyYoshi/cChardet#81) is a six month old bug showing that `cchardet` doesn't support python 3.11, which is the most recent python. `cchardet` is fast, certainly, though the usage here is not as performance sensitive as would warrant its use over `chardet`, e.g. a difference of 800ms is probably not something that is worth keeping problematic dependencies around.
cchardet doesn’t build on Python 3.11.0, and its maintainer seems to be absent. Switch to the faust-cchardet fork where this is fixed. PyYoshi/cChardet#81 Signed-off-by: Anders Kaseorg <andersk@mit.edu>
cchardet doesn’t build on Python 3.11.0, and its maintainer seems to be absent. Switch to the faust-cchardet fork where this is fixed. PyYoshi/cChardet#81 Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
This update (from 2.0.4) helped me with the issue. |
…65) * Revert "(❌) *Temporary* drop support for Python 3.11 (#41)" This reverts commit c2b568a. * Add Cython >= 3.0.0 as explicit dependency PyYoshi/cChardet#81 (comment) * Revert "Add Cython >= 3.0.0 as explicit dependency" This reverts commit f5727ef. * set min version
These are unused as of commit 14f106e (mailgun#227). cchardet doesn’t build on Python 3.11.0, and its maintainer seems to be absent (PyYoshi/cChardet#81). Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
One year later and this is still a problem... 😞 |
These are unused as of commit 14f106e (mailgun#227). cchardet doesn’t build on Python 3.11.0, and its maintainer seems to be absent (PyYoshi/cChardet#81). Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Exception caused by abandoned cchardet library: `src/cchardet/_cchardet.cpp:196:12: fatal error: longintrepr.h: No such file or directory` See also: * PyYoshi/cChardet#81 * PyYoshi/cChardet#81 (comment)
I installed Cython but cannot install twint yet. Do you have any idea helps me? |
|
python |
|
@xloc For same versions, still same error. python3.11.6, Cython 3.0.6 |
OS/Arch
$ python -c 'import platform;print(platform.uname())'Python version
3.11.0
cChardet version
Latest
$ python -c 'import cchardet;print(cchardet.__version__)'What is the problem?
Failed to build.
Expected behavior
Supposed to build.
Actual behavior
fatal error: longintrepr.h: No such file or directory
Steps to reproduce the behavior
Just update to Python 3.11 and attempt to build code results in error.
The text was updated successfully, but these errors were encountered: