-
Notifications
You must be signed in to change notification settings - Fork 42
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
Support for Python 3.11 #181
Conversation
Kudos, SonarCloud Quality Gate passed! |
Hi there, aiming to add support for Python 3.11 to the Terkin Datalogger, we had to downgrade to It looks like With kind regards, |
Hi Andreas,
I'm aware of it and keeping an eye on their repo.
There is already an issue with the fix but it hasn't been merged yet.
I was planning to write to the author in case it won't be taken care of
soon.
Regards,
Giorgio
…On Sat, 26 Nov 2022, 18:26 Andreas Motl, ***@***.***> wrote:
Hi there,
aiming to add support for Python 3.11 to the Terkin Datalogger
<https://github.com/hiveeyes/terkin-datalogger>, we had to downgrade to
mocket<3.9 (see ***@***.***
<hiveeyes/terkin-datalogger@3b8a94bb0>), in
order to make it work on Python 3.11.
It looks like http-parser is not ready for Python 3.11 yet.
With kind regards,
Andreas.
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEAXXILSDXTEFOPVER5FRTWKJI4RANCNFSM5WSLLATQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thank you! I've added a comment to benoitc/http-parser#95, and exercised the upgrade to Python 3.11 and Footnotes |
- this is a preparation step torwards 3.11 - anyway, unit tests without mocking are even better :-) Background: - mocket depends on ancient http-parser where we don't know if it is getting 3.11 soonish... - See: benoitc/http-parser@9099eac mindflayer/python-mocket#181 CMK-11556 Change-Id: I41c081f8aabd4833d647888c2b7d3d8aa3d15df4
Hi again,
With hiveeyes/terkin-datalogger@ffcffbaa26, the test suite now uses a modern version of Mocket for all Python versions <3.11, while still resorting to We know it is not an optimal solution, and this release probably lacks many features, but it was enough to satisfy our test suite, and it might help others as well. With kind regards, |
f9ebfcc
to
5e0d8a8
Compare
Hi @amotl, I replaced |
mocket currently does not work with 3.11. See these issues: mindflayer/python-mocket#181 benoitc/http-parser#95
mocket currently does not work with 3.11. See these issues: mindflayer/python-mocket#181 benoitc/http-parser#95
mocket currently does not work with 3.11. See these issues: mindflayer/python-mocket#181 benoitc/http-parser#95
Hi @mindflayer, thanks for sharing those news. I had a look at the exception message Maybe those discussions have some hints about that exception?
With kind regards, |
9316703
to
77f91f7
Compare
6e42f24
to
c87c222
Compare
f8d62a4
to
6719547
Compare
d32c7c0
to
dee5f0b
Compare
dee5f0b
to
b736f85
Compare
aaef9e7
to
4637a51
Compare
1bc6a06
to
7dbe0c5
Compare
SonarCloud Quality Gate failed.
|
http-parser
tohttptools
.aiohttp
/Python 3.11 (first time ever I added@pytest.mark.xfail
to a test). Same test works withhttpx
, so I suspect it's related to a client issue. I'll probably migrate tohttpx
as the one for testingasync/await
code.