fromlittleutilsimportstrip_required_prefix,strip_required_suffix,withattrs

fromlittleutilsimportstrip_required_prefix,strip_required_suffix

frompygments.formattersimportHtmlFormatter

frompygments.lexersimportget_lexer_by_name

frompygments.stylesimportget_style_by_name

))

defassign(**attrs):

defdecorator(f):

returnwithattrs(f,**attrs)

defno_weird_whitespace(string):

spaces=set(re.findall(r"\s",string))

assertspaces<= {" ","\n"},spaces

return''.join(traceback.format_exception_only(*sys.exc_info()[:2]))

defrow_to_dict(row):

d=row.__dict__.copy()

deld["_sa_instance_state"]

defrows_to_dicts(rows):

return [row_to_dict(row)forrowinrows]

defthread_separate_lru_cache(*cache_args,**cache_kwargs):

defdecorator(func):

defcached(_thread_id,*args,**kwargs):

returnfunc(*args,**kwargs)

defwrapper(*args,**kwargs):

returncached(threading.get_ident(),*args,**kwargs)

defis_valid_syntax(text):

try:

ast.parse(text)

**If you'd like to donate money, please do so at[open collective](https://opencollective.com/futurecoder).**

For starters, try using the platform to see what it's like.You can go straight tothe[site](https://futurecoder.io/) and quickly sign up for anaccount. See the[Controls](README.md#controls) section for instructions on enabling developer mode, this will allow you to skip or replay steps in a page to allow exploring more freely and quickly.

For starters, try using the platform to see what it's like.Fromthe[table of contents](https://futurecoder.io/course/#toc) you can jump to any page and start immediately. Noaccount needed. If you want to try all the debuggers, pick a page close to the end of the course where everything is enabled. See the[Controls](README.md#controls) section for instructions on enabling developer mode, this will allow you to skip or replay steps in a page to allow exploring more freely and quickly.

Please[open an issue](https://github.com/alexmojaki/futurecoder/issues/new) about anything that's confusing, could be done better, or doesn't work. All suggestions and feedback are welcome. Tell me what interests you!

The easiest way to contribute concretely is to write learning material for the course and participate in related discussions. This doesn't require any expertise beyond knowing how Python works. See[Helping with course content](#helping-with-course-content) for more information.

Beyond that, there's plenty of coding work to do on the platform, including frontend, backend,anddevops work. See the[list of issues](https://github.com/alexmojaki/futurecoder/issues) for some ideas, or open a new one if you want. The main priority is to choose something that interests you. If nothing really does, pick something from the["good first issue" label](https://github.com/alexmojaki/futurecoder/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - these are easier and will help you become familiar with the project.

Beyond that, there's plenty of coding work to do on the platform in PythonandJavaScript. See the[list of issues](https://github.com/alexmojaki/futurecoder/issues) for some ideas, or open a new one if you want. The main priority is to choose something that interests you. If nothing really does, pick something from the["good first issue" label](https://github.com/alexmojaki/futurecoder/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - these are easier and will help you become familiar with the project.

Consider adding your thoughts and ideas to[issues labeled 'discussion'](https://github.com/alexmojaki/futurecoder/issues?q=is%3Aissue+is%3Aopen+label%3Adiscussion). Or[come have a chat about anything on slack](https://join.slack.com/t/futurecoder/shared_invite/zt-tp8cmwra-CbdEeX9u3k1VyoMLDupAeQ).

If you make some changes to the course, the tests will likely fail the comparison to`test_transcript.json`. Run the test again with the environment variable`FIX_TESTS=1` to update the file. Then check that the git diff looks sensible.

-**Python runs in the browser with[Pyodide](https://pyodide.org/)**. There are no backend servers.

- This runs in a web worker (`Worker.js`) in the background so it doesn't interfere with the UI.

-`SharedArrayBuffer` is used for some features (`input()` and`KeyboardInterrupt`) which comes with certain restrictions, including not working on Safari.

- The entire`core` folder as well as several libraries are packaged into a single archive which the worker downloads (`load.py`) and extracts into Pyodide's virtual filesystem.

- The script`core/generate_static_files.py` creates the above archive and some other files and puts them under`frontend/src` to be packaged by React.

- When a user runs code,`Worker.js` calls the Python function`check_entry_catch_internal_errors` in`worker.py`.

- After the code finishes running, it checks the`Page` and`Step` that the user is currently on, and calls the`Step.check` method.

- In most cases this is a`VerbatimStep` - the user is supposed to enter exactly the code in the text, using the AST to check for equality.

- Next most common is an`ExerciseStep` where a function has to pass tests and produce the same output as a given solution.

- The result of`Step.check` determines if the user succeeded and advances to the next step. It may also return a message to show the user, e.g. if they made a common mistake.

-**React JS** provides the course UI.

- It's mostly just a standard Create-React-App, very slightly customised by craco.

- The UI communicates with the web worker using Comlink (`RunCode.js`).

- State is managed by Redux (`store.js`) with some custom utilities (`frontendlib`).

-**Firebase** handles:

- Authentication: signup, login, and anonymous accounts

- Realtime Database stores user data: progress on each page and last page visited

- Hosting for the main site, although since it's just static files so it can be hosted anywhere quite easily.

Take a look at[the issues labeled "course material"](https://github.com/alexmojaki/futurecoder/issues?q=is%3Aissue+is%3Aopen+label%3A%22course+material%22). These include discussions that need opinions/ideas and small tweaks that need to be made to existing content.

If you want to write fresh content, see[this issue](https://github.com/alexmojaki/futurecoder/issues/92) for the central discussion.

If you want to write fresh content, see[this issue](https://github.com/alexmojaki/futurecoder/issues/165) for the central discussion.

Before writing anything, it's a good idea to go through some of the course to get a feel for the style. Reading all the hints on a few exercises would also help. See the[developer mode instructions](https://github.com/alexmojaki/futurecoder#controls) to quickly move back and forth between steps.