Contact

Questions, corrections, and feedback are genuinely welcome — PYLI5 gets better when readers point out what’s confusing or broken. The best way to reach us is by email at [email protected].

Good reasons to get in touch:

• Corrections — something that looks wrong, out of date, or unclear in a lesson.
• Broken examples — code or a Try-It exercise that doesn’t run the way the lesson says it should.
• Lesson suggestions — a topic you wish PYLI5 covered, or a concept that needs a clearer explanation.
• Accessibility issues — anything that makes the site hard to read or use.
• General feedback — what’s working, what isn’t, and what would help you learn.

PYLI5 is a small, independent project, so replies aren’t instant — but every message is read, and corrections to lessons are prioritised. If you’re reporting a broken example, a link to the lesson and a note about what you expected to happen makes it much faster to fix.