Failed to Build on Python 3.11.0

[shubhamshah02]

OS/Arch

$ python -c 'import platform;print(platform.uname())'

Python version

3.11.0

$ python --version

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.

[ToasterUwU]

Same here.

      src/cchardet\_cchardet.cpp(196): fatal error C1083: Cannot open include file: 'longintrepr.h': No such file or directory
      error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> cchardet

[ToasterUwU]

nvm that issue mention, i made a little mistake and assumed that orjson depends on this, which it doesnt.

[lvillis]

Same here.

      src/cchardet\_cchardet.cpp(196): fatal error C1083: Cannot open include file: 'longintrepr.h': No such file or directory
      error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.32.31326\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> cchardet

[seperman]

Same here

[SimplicityGuy]

There are 2 PRs #78 and #80 that will address this. @PyYoshi, can you merge and release a new build, please?

[woctezuma]

I encounter the same issue with the cchardet package.

I have noticed it as I wanted to install ASF_IPC, which depends on two other packages:

aiohttp
cchardet

For the aiohttp package, the issue was solved in September:

• Fails to build on Python 3.11 - longintrepr.h: No such file or directory aio-libs/aiohttp#6600

[ToasterUwU]

@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.

[woctezuma]

It is definitely a bit weird that the requirements mention chardet v3.0.4 when the current version is v5.0.0, which was updated for Python v3.11.

However, I think one would have to also change other requirements, notably the version of Cython.

[seperman]

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.

[ToasterUwU]

@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

[seperman]

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.

[ToasterUwU]

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.