Python in seconde, taught by teachers who are not programmers

The problem

The French curriculum puts Python in classe de seconde, and the teachers asked to deliver it are usually not programmers. Installing Python across school machines is a project in itself, so students end up writing code on paper. And nobody could see what had been changed, by whom or when — a question could be edited after an exam had been submitted and leave no trace.

What was built

A browser platform. Students write and run real Python with nothing to install. Each lesson gives the teacher a guided path — exercises, expected output, automatic checking — so the class does not depend on the teacher being a developer. Behind that, the school gets the monitoring side: every action recorded, and every change to a lesson, an exercise or an exam question kept with its author and its timestamp, including changes made after submissions have arrived.

• Python in the browser. Students write and run real Python with nothing installed, on school machines that are usually locked down.
• A guided path for the teacher. Each lesson arrives with its exercises, its expected output and its checking, so the class does not depend on the teacher being a programmer.
• Automatic checking. Routine exercises are marked the moment they are submitted, with the failing case shown to the student.
• Every change kept. Lessons, exercises and exam questions are versioned with the author and the time — including a change made after submissions have come in.
• Roles that match the institution. School, teacher, student — each seeing only what they should, and the school seeing all of it.

Outcome

A school can teach the seconde Python curriculum without a specialist teacher and without touching its computers — and after any dispute it can answer the question that actually matters: what was changed, by whom, and when.

Project facts