Hi Irv, thanks a lot for your response. I will try.
Cheers,
Ambro
2020-04-17 19:54 GMT+02:00, Irv Kalb :
> HI,
>
> I recently brought up a similar thing on this list a couple of weeks ago. I
> am using Python 3.7 with Pygame on my Mac with no problems, but I had heard
> of problems with 3.8. Here is a response from Thomas Kluyver to my
> question:
>
> ---
> Hi Irv,
>
> If I recall correctly, the issue was that there aren't pre-built wheels for
> pygame with Python 3.8 - looking at the PyPI files
> (https://pypi.org/project/pygame/#files
> <https://pypi.org/project/pygame/#files> ), it's only built for Windows at
> the moment. So it's not incompatible, but it's more complicated to install
> it on Linux & Mac than if you use Python 3.7.
>
> From what you say, a setup that you know works is probably preferable to
> using the latest Python version.
>
> Best wishes,
> Thomas
>
>
> So, if possible, I would downgrade your Python to 3.7.x and see if that
> fixes this problem.
>
> Irv
>
>> On Apr 16, 2020, at 3:24 PM, Ambrogio Riili wrote:
>>
>> Hello everybody. I hope it's the right place for this report. I would
>> like to report a problem in Pygame for Mac. I also use Windows and I
>> have no problem. However for Mac the situation has worsened
>> significantly. First of all, to install Pygame on Mac I followed a
>> long procedure, because pip alone could not install it and gave error.
>> But once this procedure is finished, Pygame has installed itself,
>> however every game created with Pygame does not receive keyboard
>> inputs. Could you solve in the next versions? I leave you here all my
>> specifications and the only way I have found to solve it on Mac.
>> Thank you,
>> Ambro
>>
>> macOS Catalina 10.15.4
>> python 3.8.2
>> pygame 1.9.6 (but I have tried different versions, from 1.9.4 onwards)
>> The only method I found to solve the problem I read on a forum, where
>> a user proposed to install pyobjc (pip install pyobjc) and then add
>> these lines:
>>
>> from AppKit import NSApplication
>> NSApplication.sharedApplication().setActivationPolicy_(0)
>>
>
>
