-
Notifications
You must be signed in to change notification settings - Fork 370
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
Build wheels for Python 3.12 #1168
Comments
I'm closing this because I fixed this myself in my fork, pyav. You can switch by simply replacing I highly recommend everyone to switch because it's a bad idea to use a library that is not being maintained. |
All the necessary PRs are merged. The only step left is make release. @jlaine? |
I've tagged |
It looks like we've hit the dreaded 10GB limit on PyPI. We should ask for an increase then redo the release.
|
As I don't own the project, unfortunately I can't clean up old releases. I have filed an issue with PyPI in pypi/support#3324. EDIT: we don't need to redo the release, we'll just need to rerun the failed "publish" task once the size limit is addressed. @mikeboers : could you make me an owner of the |
I have tried deleting the wheels of two releases (8.0 and 8.0.1) but I'm still getting the "project too large" error.. Let's hope PyPI support raises the limit. |
I deleted even more files and this time the upload went through. We'll be stuck again at the next release though.. |
Could you please provide wheels for Python 3.12? |
We don't control that namespace |
Thanks for explanation, there is URL leading to this project. It turns out it's a fork... |
Thanks a lot @WyattBlue and @jlaine for solving this issue! Your work is highly appreciated ❤️ I was wondering if you are also planning to update the Apologies if this is not the right place to ask. |
Python3.12 is now released and the default choose for users who download python via python.org
I would also highly suggestion merging PR #1145 and #1110 so that building from source is a viable option.
The text was updated successfully, but these errors were encountered: