Odd. Most times i've seen that particular line of code written differently though, such as "for events in pygame.event.get()". You could try resetting your system, or try troubleshooting it with your own python script.

Pretty sure this error has something to do with the Python interpreter itself. In C/C++, when an exception is raised on the Python side, the python C API sets the error indicator. It is up to the consumer of the C API to check this indicator and to handle it as necessary. I'm pretty sure that this error is  caused because for whatever reason this isn't being done, and so Python is, naturally, complaining about it because the code is trying to keep going when an exception occurred on the Python side of things. I'd recommend just switching to Raylib via raylibpy or another library for the games you write because you won't be able to do anything with Pygame until this gets fixed, which could take who knows how long. As for all other games that use Pygame, well, not much you can do about that.

@6, it definitely is. If your used to the BGT way of doing things though you'll definitely have to rethink how you write games though. It's worth noting that if you do use it, your game loop must call BeginDrawing/EndDrawing regardless of whether you actually draw anything or not (EndDrawing in particular does all the event handling and stuff). You can set up a function to throw exceptions on Raylib errors by just calling SetTraceLogCallback, which is also nice, because by default the library logs everything to stdout (though if you don't like having try/except everywhere you don't have to obviously). An alternative to Begin/EndDrawing is if you want full frame control you can first call SwapScreenBuffer, then PollInputEvents, and then WaitTime, but I'd just call EndDrawing and let it do all that for you.