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
Installation fails on Python 3.11.0 #3522
Comments
This is not exactly a bug, it's that there are no release wheels yet for 3.11, use |
Was able to duplicate this issue with:
I do have a question, if there is no wheel made for Python3 3.11.0, is installing |
@arknaut Well, that's the latest version of |
@Matiiss - Okay thanks! (just clarifying) |
Uh, no, it's more like |
@Matiiss - Okay got it, thanks! |
|
Are there any updates on this? Or an ETA for the new Pygame version? |
Nope.
…On Thu, 3 Nov 2022, 08:51 Florian Krause, ***@***.***> wrote:
Are there any updates on this? Or an ETA for the new Pygame version?
—
Reply to this email directly, view it on GitHub
<#3522 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGDGGSOU7BF4KFLAR4732LWGN4IXANCNFSM6AAAAAARQJB5DY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hello everyone. I observe the same problem on Armbian
|
@rammfire if you read a few messages above, Matiiss gave the solution |
Unfortunately this is not really a solution for other packages that depend on Pygame. For instance, I am about to release a new version of Expyriment, which depends on Pygame, and I am currently mainly holding it back due to this issue. Would be great to have some idea on when proper Python 3.11 support is planned (roughly, like within the next few days, or will it still be months?). |
@fladd The full release of 2.1.3 is almost out. I'm hoping it'll be within a week or two at most, but that's really up to the discretion of the lead maintainer right now |
Cant wait for the full release ! 😄 |
Though Looking forward to pygame-2.1.3.
|
Thank you so much!!! |
Can confirm this works. (Tested on Win10) |
I would advocate for a point release that basically doesn't change anything from the previous, but simply provides wheels for the new python version. A lot of beginners will get caught up on this while a new patch release is prepared. e.g., 2.1.3 simply ships additional 3.11 wheels, 2.1.4 gets moved to new patch release. |
To the best of my knowledge, 2.1.3 is ready for release. Just waiting on the head maintainer to actually release it. |
Since it has been over a month now: Is there any news regarding the release? |
To the best of my knowledge, the lead maintainer has not said anything to anyone in that time. Nobody else has the ability to release 2.1.3, so unfortunately we’re stuck waiting |
@illume Python 3.11 has been out for a month and a half (and pygame's |
I've tried and tried, but can't even instal the pre-release.
|
Are you sure you are using the pip from python 3.11 there? Pis come with
multiple python versions. I thought you had to use pip3 on there
…On Sat, 17 Dec 2022, 11:38 Michael Naylor, ***@***.***> wrote:
I've tried and tried, but can't even instal the pre-release.
RPi 4B, Bullseye (64-bit), Python3.11.
***@***.***:~/pgtest $ pip install pygame --pre
Collecting pygame
Downloading pygame-2.1.3.dev8.tar.gz (12.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 12.1/12.1 MB 2.8 MB/s eta 0:00:00
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [33 lines of output]
WARNING, No "Setup" File Exists, Running "buildconfig/config.py"
Using UNIX configuration...
/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
/bin/sh: 1: sdl2-config: not found
Traceback (most recent call last):
File "<string>", line 2, in <module>
File "<pip-setuptools-caller>", line 34, in <module>
File "/tmp/pip-install-9_sp3ju8/pygame_06121d1e121e4eafb99504b0ad01a83b/setup.py", line 399, in <module>
buildconfig.config.main(AUTO_CONFIG)
File "/tmp/pip-install-9_sp3ju8/pygame_06121d1e121e4eafb99504b0ad01a83b/buildconfig/config.py", line 231, in main
deps = CFG.main(**kwds, auto_config=auto)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/tmp/pip-install-9_sp3ju8/pygame_06121d1e121e4eafb99504b0ad01a83b/buildconfig/config_unix.py", line 189, in main
DependencyProg('SDL', 'SDL_CONFIG', 'sdl2-config', '2.0', ['sdl']),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/tmp/pip-install-9_sp3ju8/pygame_06121d1e121e4eafb99504b0ad01a83b/buildconfig/config_unix.py", line 39, in __init__
self.ver = config[0].strip()
~~~~~~^^^
IndexError: list index out of range
Hunting dependencies...
---
For help with compilation see:
https://www.pygame.org/wiki/Compilation
To contribute to pygame development see:
https://www.pygame.org/contribute.html
---
[end of output]
note: This error originates from a subprocess, and is likely not a problem
with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
—
Reply to this email directly, view it on GitHub
<#3522 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGDGGRVNWTT24EY5AYKHATWNWQ4BANCNFSM6AAAAAARQJB5DY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think so. Both 'pip' and 'pip3' report version 22.3.1 from the same 'penv global 3.11.0'. |
Ah, I suspect it is because the pi is looking on the piwheels repository instead of PyPI and it won't find any 3.11 wheels on piwheels because piwheels only builds wheels for a maximum of python 3.9.
Otherwise you will have to learn to build pygame from source if you want to use 3.11 on a raspberry PI. |
Had same error. Used temporary fix. Please, please, please post this solution on the homepage of Pygame! I'm an experienced coder but new to python and spent several hours thinking I had done something wrong. |
Unfortunately, the only person with access to the pygame.org website is the same person that can fix this whole mess in the first place. But, they’ve been unresponsive so far. |
Bummer. First installs always seem to go sideways. :-( |
Did you try to run |
Thank you! This little detail helped a lot. |
I'm also trying to install from source at the moment and I'm getting the following error:
The pre-release wheel does work for me though. |
thx!
thx! |
FYI: pygame 2.1.3 had just been released with support for Python 3.11. A bit thank you to the maintainers! I think this can be closed. |
Nice, I updated my pygame now. C:\Users\Liu.D.H>pip install -i https://pypi.tuna.tsinghua.edu.cn/simple -U pygame
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Requirement already satisfied: pygame in c:\users\liu.d.h\appdata\local\programs\python\python311\lib\site-packages (2.1.3.dev8)
Collecting pygame
Downloading https://pypi.tuna.tsinghua.edu.cn/packages/23/c4/64a649c9c9dc649c8c01d7f1027c0656155fc48ba17e6fdd2cb38a993610/pygame-2.1.3-cp311-cp311-win_amd64.whl (10.4 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 10.4/10.4 MB 6.4 MB/s eta 0:00:00
Installing collected packages: pygame
Attempting uninstall: pygame
Found existing installation: pygame 2.1.3.dev8
Uninstalling pygame-2.1.3.dev8:
Successfully uninstalled pygame-2.1.3.dev8
Successfully installed pygame-2.1.3
C:\Users\Liu.D.H> |
Failed to install pygame. There is an error in pypm compilation, saying "too many initializers". building 'pygame.pypm' extension C:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\bin\HostX86\x64\cl.exe /c /nologo /O2 /W3 /GL /DNDEBUG /MD -Iprebuilt-x64/SDL2-2.24.2/include -Iprebuilt-x64/include -Ic:\usr\dev\python\include -Ic:\usr\dev\python\Include -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\include -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\ATLMFC\include -IC:\usr\dev\msvs2022\VC\Auxiliary\VS\include "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\cppwinrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\include -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\ATLMFC\include -IC:\usr\dev\msvs2022\VC\Auxiliary\VS\include "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\cppwinrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\include -IC:\usr\dev\msvs2022\VC\Tools\MSVC\14.36.32532\ATLMFC\include -IC:\usr\dev\msvs2022\VC\Auxiliary\VS\include "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\cppwinrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" /Tcsrc_c/pypm.c /Fobuild\temp.win-amd64-pypy310\Release\src_c/pypm.obj /W3 /wd4142 /wd4996 /GF /Gy pypm.c src_c/pypm.c(3770): warning C4244: 'function': conversion from 'Py_ssize_t' to 'int32_t', possible loss of data |
Environment:
You can get some of this info from the text that pops up in the console when you run a pygame program.
Current behavior:
pip install pygame fails
Expected behavior:
above command succeeds
Steps to reproduce:
Please explain the steps required to duplicate the issue, especially if you are able to provide a sample application.
if the bug is caused by a specific file (image, font, sound, level, please upload it as an attachment
Stack trace/error output/other error logs
The text was updated successfully, but these errors were encountered: