To help you get started, we've collected the most common ways that skulpt is being used within popular public projects.

uccser / cs-field-guide / csfieldguide / static / interactives / python-interpreter / js / python-interpreter.js View on Github

$("#interactive-python-interpreter-run").click(function(){
        var program = document.getElementById("interactive-python-interpreter-code").value;
        var output = document.getElementById("interactive-python-interpreter-output");
        output.innerHTML = '';
        Sk.configure({output:skuplt_out});
        try {
            Sk.importMainWithBody("", false, program);
        } catch (e) {
            alert(e);
        }
    });

View more ways to use skulpt

Welcome to Skulpt

Skulpt is a Javascript implementation of Python 2.x. Python that runs in your browser! Python that runs on your iPad! Its being used several projects including, Interactive Python Textbooks -- You can see skulpt in action there. Try out some turtle graphics examples to see Skulpt in action.

Origins

Skulpt is the brainchild of Scott Graham. See Skulpt.org for some early demos of skulpt in action.

Brad Miller has been project maintainer since sometime in 2010/2011 along with core contributors Albert-Jan Nijburg, Scott Rixner, Meredydd Luff and others.

Current Priorities

• We have updated our development toolchain to include nodejs and webpack. If you have been a developer in the past make sure you check out the documentation for the current procedures on building skulpt.
• Work on Python3 - With python 2 coming to the end of its life at the end of this year, being more and more Python3 compliant is a high priority. Of course how Python3 you need to be depends on the situation. For many uses, Skulpt is already there. But for more advanced work we are not. You can keep up with this work by configuring skulpt to run in Python3 mode.

Sk.configure({
    .... other settings
    __future__: Sk.python3
});

How can I help?

Welcome to the Skulpt developer community! We welcome new developers of all levels and abilities. Check out the ideas list below. And then some practical things for getting started after that.

Ideas List

1. Python 3 -- see above.

2. Expand the skulpt standard library to include more modules from the CPython standard library. So far we have math, random, turtle, time (partial) random (partial) urllib (partial) unittest, image, DOM (partial) and re (partial). Any of the partial modules could be completed, or many other CPython modules could be added. Potential new modules from the standard library include: functools, itertools, collections, datetime, operator, and string. Many of these would be relatively easy projects for a less experienced student to take on.

3. Over time we have had numerous requests for more advanced Python modules to be included in Skulpt. These include, portions of matplotlib, tkinter, and numpy. These are much more challenging because they contain C code in their implementation, but if a reasonable subset could be implemented in Javascript this would make it much easier to directly add many more python modules that rely on these three. In addition, it would allow for skulpt to potentially be used in teaching an even broader set of topics.

4. Expand and clean up the foreign function API. This API is critical for implementing parts of the standard library.

5. Do a better job of supporting Python3 semantics, but make Python2/Python3 behavior configurable with a single flag. Sk.python3 is already there for this purpose. Another positive step in this direction would be to update our grammar to Python2.7. Updating the grammar would allow us to add set literals, dictionary comprehensions, and other features present in 2.7.x and Python 3.3.x. This would be an excellent project for a student interested in language design, parsing, and the use of abstract syntax trees.

6. Make fully workable, and expand support for DOM access as part of the standard library.

7. Expand and improve overall language coverage. Currently Skulpt does an excellent job of meeting the 80/20 rule. We cover the vast majority of the language features used by the 80% (maybe even 90%) of the code. But there are builtins that are not implemented at all, and there are builtins with only partial implementations.

8. Implement the hooks for a debugger. This may be a half step towards 1 or may be in a completely different direction, but allowing students to debug line by line a program they have written would have some real benefit.

Building Skulpt

Building Skulpt is straightforward:

1. Clone the repository from GitHub, ideally using your own fork if you're planning on making any contributions
2. Install node.js
3. Install the required dependencies using npm install
4. Navigate to the repository and run npm run dist
5. The tests should run and you will find skulpt.min.js and skulpt-stdlib.js in the dist folder

Contributing

There is plenty of work still to do in making improvements to Skulpt. If you would like to contribute

1. Create a Github account if you don't already have one
2. Create a Fork of the Skulpt repository -- This will make a clone of the repository in your account. DO NOT clone this one. Once you've made the fork you will clone the forked version in your account to your local machine for development.
3. Read the HACKING.md file to get the "lay of the land". If you plan to work on creating a module then you may also find this blog post helpful.
4. Check the issues list for something to do.
5. Follow the instructions above to get skulpt building
6. Fix or add your own features. Commit and push to your forked version of the repository. When everything is tested and ready to be incorporated into the master version...
7. Make a Pull Request to get your feature(s) added to the main repository.

Community

Check out the mailing list: https://groups.google.com/forum/?fromgroups#!forum/skulpt

Acknowledgements

As time goes on its getting more dangerous to try to acknowledge everyone who has contributed to the project. And, after all, this is git, so their names are all in the historical record. But there are a few to call out.

• First and foremost to Scott Graham for starting the original project.
• Bob Lacatena for lots of work on Python longs
• Charles Severence for bug fixes and the re module.
• Leszek Swirski and Meredydd Luff for Suspensions
• Albert-Jan Nijburg for countless bug fixes and process improvements
• Ben Wheeler for the new and improved turtle module
• Scott Rixner and students for many bug fixes and improvements
• Of course, The complete list is here: https://github.com/skulpt/skulpt/graphs/contributors