-
Notifications
You must be signed in to change notification settings - Fork 772
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 Python 3.11 #1572
Comments
I've just tested pyqrcode on Python 3.11, works: Yes, pyqrcode should probably move to pytest or similar, a "standard" Python test tool. Please report to upstream. Apart from that, the real issues pop up with
aio-libs/aiohttp#6600 These can be worked around with
Created a PR for that ethereum/eth-typing#29 Similar for web3. At this point, I gave up for now ... lots of projects are only just now adjusting to py 3.11, and I don't need it now |
I'm sorry but I left my time machine in the other pants' pocket. |
Part of the deps of autobahn[all] install web3, and of the web3 deps
this one fails
as does this
with the same error
|
so the actual reason is |
I;m sorry but why did you hijack my bug report? |
Because Autobahn should run on Python 3.11 - and it doesn't, but not because of pyqrcode, but because of above.
I don't use Gentoo, and from my point of view, the whole approach of distributing Python packages as OS packages is "wrong" - but sure, I am aware, this is probably non-mainstream opinion. I agree about pyqrcode btw: it could need a maintainer, proper refresh etc. - or, indeed, replacing it with sth else - if s.o. comes up with a PR .. We still need a bug to track autobahn[all] on Python 3.11 .. sorry for hijacking! |
Made #1573 for that. |
replace pyqrcode with qrcode (see #1572)
I think we can close this now as 3.11 support was fixed for asyncio. Didn't test twisted though |
This works now, so issue can be closed. |
pyqrcode has not received a single commit since 2016. It still uses nosetests, and after being abandoned for equally as long they no longer work on Python 3.11. This effectively means this dependency is a lot of pain for distributions that can't test these packages properly.
The text was updated successfully, but these errors were encountered: