Contributor Troubleshooting

Contributor Troubleshooting

The wrong package or command is running

The distribution and command are named pythonlings. The similarly named pylings package is unrelated. In a source checkout, install the project into the interpreter you plan to use:

python -m pip install -e ".[dev]"
python -m pip show pythonlings
pythonlings --version

If the command still resolves to another environment, activate the intended virtual environment and repeat the editable install with that environment's python. Check the shell's command resolution before assuming a source change is not being used.

A source checkout is being used as a learner workspace

Workspace resolution treats a current directory containing info.toml as a workspace. A repository checkout therefore qualifies, but it is source material and should not be used for ordinary learner edits. Use a separate workspace for learner work, or pass the intended location explicitly with --root. This avoids mixing learner progress and edits with a contribution checkout.

A curriculum addition does not load or verify

Most curriculum failures are incomplete synchronization. Check the exercise, mirrored check, solution loader, _answers.py entry, and ordered info.toml entry together. A missing or mismatched path is rejected when the manifest loads; a missing solution is rejected during solution verification. See the Curriculum Authoring Guide for the complete checklist.

An update did not replace an exercise

This is expected. Workspace updates preserve existing learner exercise files while refreshing managed material such as checks, solutions, manifest data, and reset snapshots. Use the reset flow when restoring a particular exercise is intended. A .bak state file has a different purpose: it is created only to preserve an unreadable progress-state file before starting with fresh state.

Where to report a problem

• Use GitHub Issues for reproducible defects and scoped work.
• Use GitHub Discussions for questions and broader ideas.
• Report vulnerabilities privately through GitHub Security Advisories, as required by the Security Policy.
• Report Code of Conduct concerns through the route in the Code of Conduct.