IronLanguages / IronLanguages/ironpython3

IronPython.Runtime.Exceptions.ImportException: 'No module named 'pygame''

Open
#1,674 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

not supported - CPython extension
Dominant language
C#
Stars
2.8k
Forks
316
Avg merge
1d 9h
Merged PRs (30d)
1

Description

Prerequisites

The issue tracker is used to report bugs and request new features, NOT to ask questions.

Questions should be posted in Discussions or to the users mailing list which can be accessed at
https://ironpython.groups.io/g/users.

  • Are you running the latest version?
  • Are you reporting to the correct repository?
  • Did you perform a cursory search?
Description

I downloaded the pygame package using the pip virtual environment, and copied the entire Lib folder generated by the pip virtual environment to the Debug folder and referenced it in the program. However, why would an error be reported?

001

Steps to Reproduce
  1. Install Ironpython 3.4 in nuget package manager
  2. Run "python - m venv env" to create a python virtual environment
  3. Run "env Scripts activate. bat" to enable the Python virtual environment
  4. Run "pip install pygame" to download the latest package for pygame
  5. Copy the Lib folder under the env folder created by pip to the project output path
Versions

IronPython 3.4
Python 3.9 (64-bit)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the IronPython 3.4 NuGet setup with a Python 3.9 64-bit virtual environment, pygame, and the copied Lib folder; use the resulting import error to determine the supported package-loading behavior and define a reproducible fix or documentation update.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.