-
-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cchardet requirement, Python 3.11 compat #922
Comments
Stupid question, sorry. I was using ripgrep and not grep, which skipped the relevant files. |
@pansen - Notwithstanding your "stupid question" 😜 I think this issue should be re-opened. Cryptofeed does not build out-of-the-box on 3.11.0 and it does indeed seems that cchardet is the culprit.
Potential solutions:
Regarding (2), there is a note in setup.py that cchardet is optional. Cryptofeed does indeed build (and run) when using the Python chardet. @bmoscon: thoughts on abandoning cchardet in favour of Python chardet? (In terms of speed gained using Python 3.11 plus speed lost by not using Cchardet?) Is there perhaps some clever way to conditionally install Python chardet if Python version ≥ 3.11 else Cchardet? Temporary solutions: |
I was able to get it working with 3.11, what error do you get? |
I pasted the error above |
My setup was Python 3.11 within Conda env, running on Mac. It wouldn't build from either source or pip |
resolved with latest commit |
Hi,
first: thank you for your great library. I much enjoy using that :)
With the release of Python 3.11 I was checking my projects upgrade capabilities and it turns out, that cchardet is a difficult candidate. There is already an open issue for Python 3.10 (how is this working for Python 3.10 then anyway ...) and the project seems not maintained anymore.
In the sourcecode of cryptofeed I was looking for places where cchardet is actually used, as I wanted to see if it can be replaced with charset-normalizer (via SO) but couldn't find the location.
So my questions are:
Best, Andi
The text was updated successfully, but these errors were encountered: