Awesome

<p align="center"> <a href="https://github.com/alexmojaki/futurecoder/blob/master/LICENSE.txt"><img src="https://img.shields.io/github/license/alexmojaki/futurecoder?style=flat" alt="MIT license" align="left"></a> <a href="https://github.com/alexmojaki/futurecoder/actions"><img src="https://github.com/alexmojaki/futurecoder/workflows/CI/badge.svg" alt="Tests status" align="left"></a> <img src="homepage/static/logo/bordered2.png" width="300px" height="300px" alt="logo"> <a href="https://saucelabs.com"><img src="https://opensource.saucelabs.com/images/opensauce/powered-by-saucelabs-badge-gray.png?sanitize=true" alt="Testing Powered By SauceLabs" align="right"></a> </p> <h1 align="center"><code>futurecoder</code></h1>

This is a 100% free and interactive course for people to teach themselves programming in Python, especially complete beginners at programming. It is carefully designed to reduce frustration and guide the user while still ensuring that they learn how to solve problems. The goal is for as many people as possible to learn programming.

You can try it out here: https://futurecoder.io/

Please consider contributing or donating!

Alternatively, come have a chat on slack.

Features

For a fuller demonstration and explanation, watch this video.

<table> <tr> <td colspan="2"> The course is a fully interactive 'book' which requires the user to run code in the provided editor or shell to advance: </td> </tr> <tr> <td colspan="2">

full </td>

</tr> <tr> <td> This requires a mixture of solving problems or simply typing and running provided code. In the latter case, the user is often kept engaged by being asked to predict the output in a simple multiple choice question: </td> <td> The code at each step is checked automatically. If needed, the student can get small hints to gradually guide them to the solution: </td> </tr> <tr> <td>

predict_output </td> <td>

hints </td>

</tr> <tr> <td> If they're still really stuck, they can reveal the solution bit by bit: </td> <td>

Or in some cases solve a Parsons problem instead, where they have to put a shuffled solution in the correct order:

</td> </tr> <tr> <td>

solution

</td> <td>

parsons

</td> </tr> <tr> <td> Tracebacks are more helpful than usual, with several enhancements:

Highlighting the exact operation that failed, not just the line, using executing
Tables of local variables and simple expressions evaluated by pure_eval
Suggestions for fixes provided by DidYouMean
Beginner friendly explanations provided by friendly-traceback (shown when hovering over the little i icon)
Showing multiline statements in full thanks to stack_data without showing unnecessary extra lines

</td> <td> Common mistakes can be caught and pointed out to the student. This includes specific checks in some steps as well as linting tailored for beginners. </td> </tr> <tr> <td>

traceback

</td> <td>

executing

</td> </tr> <tr> <td>

Several debuggers are provided, including snoop... </td> <td>

...birdseye... </td>

</tr> <tr> <td>

snoop </td> <td>

birdseye </td>

</tr> <tr> <td colspan="2">

...and Python Tutor </td>

</tr> <tr> <td colspan="2">

pythontutor </td>

</tr> </table>

Running locally

Fork this repo, git clone it, and enter the top-level futurecoder folder.
Install Python 3.12.1 and poetry.
Run poetry install to install Python dependencies.
Run ./scripts/generate.sh. This will generate various static files from Python used by the frontend and run some tests. Repeat this step whenever you change Python files.
In the frontend folder:
1. Install node. We recommend using version 16.17.1 (lts/gallium) but there are no known issues with other versions.
2. Run npm ci to download dependencies.
3. Run npm run build and then copy service-worker.js from the course folder to the public folder. The service worker is used by sync-message to handle time.sleep and reading from stdin (e.g. input()) in Python. If you want to enable caching (not a good idea when developing), set the environment variable REACT_APP_PRECACHE=1 when building.
4. Run npm start to start the frontend development server.
Go to http://localhost:3000/course/

To learn more about the system, see the contributing guide.

Controls

To explore the course more freely:

Click the hamburger menu icon in the top left.
Click Settings.
Turn Developer mode on.
This should give you two red buttons floating at the bottom of the screen. They change the currently active step, so you can move forward without having to complete exercises or backwards to test a step again.