pygame

library2.6.1pypypi✓ verified 28d ago

Pygame is a set of Python modules designed for writing video games. It leverages the Simple DirectMedia Layer (SDL) library, providing cross-platform access to your computer's multimedia hardware, such as sound, video, mouse, keyboard, and joystick. The current stable version is 2.6.1, with frequent minor and bugfix releases, often bundling updates to the underlying SDL library.

devops testing observability

pip install pygame

github ↗package ↗homepage ↗docs ↗

INSTALL

IMPORT

SIG · PYGAME

pygame

devopspythonv2.6.1

Install

2.5s avg

Import

312ms

Disk

52MB

Pass rate

5/ 10

Env Coverage5 / 10

glibc

3.9–3.13

musl

3.9–3.13

Install & Compatibility

Where this runs

tested against v2.6.1 · pip install

no network on importno background threads

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

py 3.10–3.95 runs

build_error

glibc

py 3.10–3.95 runs

installs and imports cleanly · install 2.5s · import 0.312s · 53MB

52MB installed

● package 52MB

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

pygame

✓ import pygame

init

✓ pygame.init()

display

✓ pygame.display.set_mode((width, height))

event

✓ for event in pygame.event.get():

image

✓ pygame.image.load('path/to/image.png')

time

✓ pygame.time.Clock()

This quickstart code initializes Pygame, creates a window, draws a red square on a white background, and handles the basic event loop for closing the window. It demonstrates essential components like initialization, display setup, event handling, drawing, and display updates.

import pygame pygame.init() WIDTH, HEIGHT = 800, 600 SCREEN = pygame.display.set_mode((WIDTH, HEIGHT)) pygame.display.set_caption("Pygame Quickstart") WHITE = (255, 255, 255) RED = (255, 0, 0) running = True clock = pygame.time.Clock() FPS = 60 player_rect = pygame.Rect(WIDTH // 2 - 25, HEIGHT // 2 - 25, 50, 50) while running: for event in pygame.event.get(): if event.type == pygame.QUIT: running = False # Drawing SCREEN.fill(WHITE) # Fill the background pygame.draw.rect(SCREEN, RED, player_rect) # Draw a red square pygame.display.flip() # Update the full display Surface to the screen clock.tick(FPS) # Control frame rate pygame.quit()

Debug

Known issues

gotchaForgetting to call `pygame.init()` at the beginning of your script can lead to `pygame` modules being uninitialized, causing errors or unexpected behavior. Similarly, omitting `pygame.quit()` at the end can leave system resources tied up.

fix

Always call `pygame.init()` before using any Pygame functions and `pygame.quit()` when your application is done to properly free resources.

affects: All versions

gotchaNot regularly processing the event queue with `pygame.event.get()` or `pygame.event.pump()` inside your game loop will cause the window to become unresponsive and can lead to a "not responding" state, especially on Windows.

fix

Ensure `pygame.event.get()` is called at least once per frame to process user inputs and system events.

affects: All versions

gotchaAfter drawing to the screen, you must call either `pygame.display.update()` or `pygame.display.flip()` to make the changes visible to the user. Forgetting this will result in a blank or static screen.

fix

End each frame of your game loop with `pygame.display.flip()` (for full screen update) or `pygame.display.update(rect_list)` (for partial updates).

affects: All versions

gotchaFor optimal performance, especially with frequently blitted images, loaded `pygame.Surface` objects should be converted to the display surface's pixel format using `.convert()` or `.convert_alpha()` (for images with transparency) immediately after loading.

fix

After `image = pygame.image.load("my_image.png")`, call `image = image.convert()` or `image = image.convert_alpha()` depending on whether the image has transparency.

affects: All versions

Errors

Common errors & fixes

ModuleNotFoundError: No module named 'pygame'

Pygame is not installed in the Python environment being used, or the Python interpreter in your IDE is not correctly configured to use the environment where Pygame is installed.

fix

Install Pygame using pip in your terminal: `pip install pygame`. If using an IDE like VS Code or PyCharm, ensure the correct Python interpreter (the one with Pygame installed) is selected for your project.

pygame.error: video system not initialized

A display-related function (e.g., `pygame.display.set_mode()`, `pygame.display.set_caption()`, `pygame.display.update()`) is called before `pygame.init()` or `pygame.display.init()` has been successfully executed.

fix

Ensure `pygame.init()` (which initializes all Pygame modules) or specifically `pygame.display.init()` is called at the very beginning of your script, before any operations that interact with the display.

pygame.error: mixer not initialized

Sound and music functions (e.g., `pygame.mixer.Sound()`, `pygame.mixer.music.load()`, `pygame.mixer.music.play()`) are called without explicitly initializing the Pygame mixer module.

fix

Call `pygame.mixer.init()` after `pygame.init()` and before loading or playing any sounds or music. While `pygame.init()` initializes most modules, explicitly calling `pygame.mixer.init()` ensures the sound system is ready.

pygame.error: font not initialized

Text rendering functions (e.g., `pygame.font.SysFont()`, `pygame.font.Font()`) are used before the `pygame.font` module has been initialized.

fix

Call `pygame.font.init()` after `pygame.init()` and before attempting to create or render any fonts. `pygame.init()` usually covers this, but explicit initialization might be needed if `pygame.init()` failed or was skipped for specific modules.

pygame.event.get() is not returning any event / event.key not working

The Pygame event queue is not being processed correctly within the main game loop, often due to `pygame.event.get()` being called multiple times in a single frame, or not at all, leading to events being missed or the window becoming unresponsive.

fix

Ensure `for event in pygame.event.get():` is called exactly once per iteration within your main game loop to process all pending events. Avoid calling `pygame.event.get()` more than once in a single frame to prevent event loss.

Upgrade

Version history

2.6.1latest on PyPI · released Sep 29, 2024

Audit

Dependencies

No dependency data recorded yet.

Agent activity

67 hits · last 30 days

node

OpenAI (training)

Amazon

Resources

githubhttps://github.com/pygame/pygame ↗

packagehttps://pypi.org/project/pygame/ ↗

homepagehttps://www.pygame.org ↗

docshttps://pygame.org/docs ↗