使用导入Pygame的脚本生成Space-Invaders游戏EXE文件后运行报错的技术求助

Hey, I’ve run into this exact headache with Pygame and PyInstaller before—let’s break down what’s going wrong and how to fix it. The core issue here is how --onefile handles file paths: when you use this flag, PyInstaller packages everything into a single EXE that extracts itself to a hidden temporary folder (like %temp%\_MEIXXXXXX on Windows) when you run it. Your game is probably using relative paths to load assets (e.g., assets/ship.png), which looks for the folder right next to the EXE—but the actual assets are sitting in that temp folder, not the dist directory. Even copying assets to dist won’t help because the single-file EXE doesn’t check there.

Here’s how to fix it step by step:

1. Update Your Code to Handle Packaged Paths #

Add a helper function to your spaceinvaders.py that automatically detects whether the script is running as a packaged EXE or in your dev environment, then returns the correct asset path. Stick this at the top of your script:

import sys
import os

def get_resource_path(relative_path):
    """Get absolute path to resource, works for dev and PyInstaller builds"""
    try:
        # PyInstaller stores temp folder path in _MEIPASS when running the EXE
        base_path = sys._MEIPASS
    except Exception:
        # If running in dev, use the current working directory
        base_path = os.path.abspath(".")

    return os.path.join(base_path, relative_path)

Now, replace every instance of direct relative asset paths with this function. For example:

# Instead of pygame.image.load("assets/player.png")
player_img = pygame.image.load(get_resource_path("assets/player.png"))

2. Adjust Your PyInstaller Command to Bundle Assets #

You need to explicitly tell PyInstaller to include the assets folder in the package. Use the --add-data flag (note: Windows uses ; to separate source/destination, Mac/Linux use :):

For Windows: #

pyinstaller spaceinvaders.py --onefile --noconsole --add-data "assets;assets"

For Mac/Linux: #

pyinstaller spaceinvaders.py --onefile --noconsole --add-data "assets:assets"

This command tells PyInstaller to take your project’s assets folder and replicate its structure inside the packaged EXE.

3. Test the Fix #

After rebuilding the EXE, you can delete the assets folder from the dist directory—you won’t need it anymore, since everything is bundled inside the EXE. Run the EXE, and it should load assets correctly from the temp folder PyInstaller creates.

If you’re still stuck, add a quick debug print to check where the script is looking for assets:

print("Looking for assets at:", get_resource_path("assets"))

This will show you the exact path the script is using, making it easy to spot any mismatches.

内容的提问来源于stack exchange，提问作者jiriki79