Skip to content

vbe0201/3DS.py

Repository files navigation

3DS.py

Build Status

3DS.py is a WIP port of the Python 3.6.9 interpreter to the Nintendo 3DS. It allows you to run your Python scripts directly on the 3DS by having the interpreter embedded into a homebrew application that launches a main.py script from the same directory.

3DS.py in action

Installation & Usage

Just grab one of the releases over here and unzip it. Copy the entire 3DS.py folder to the 3ds directory of your SD card and navigate into it. You should see a 3DS.py.3dsx application.

The same directory also contains the entire Python standard library and a main.py file. To run your own projects, copy all source files into the 3DS.py directory and "start" your application from within the main.py file as this is the entry point to any Python homebrew.

Compiling

If you want to compile from source, it is required to set up a devkitARM development environment first. Next, you need to install the zlib portlib by running (dkp-)pacman -S 3ds-zlib. Otherwise you will get linker errors for the zlib module. Then cd into the 3DS.py directory and run make to build the binaries and a statically linked Python library with the corresponding header files for building Python C modules.

If you're on macOS, make sure to have gnu-sed installed. brew install gnu-sed

Homebrew that uses 3DS.py

A list of cool homebrew projects that make use of 3DS.py. Want yours to be listed here? PR them.

Development & Support

Need help? Or want to have an active voice in development of and around this project? Then join our Discord guild which focusses on homebrew development for the Nintendo 3DS in Python.

This way, things can be discussed more directly and you'll likely get answfers to your questions faster than through GitHub issues.

Special thanks

In no particular order, I want to credit these amazing people for their contributions.

  • 3DBrew for their extensive documentation and research pertaining to the 3DS.

  • devkitPro for their devkitARM toolchain.

  • smea for the ctrulib project.

  • David Buchanan for troubleshooting assistance.

  • Fenrir for his support and the ctru-rs project that helped me out with the condition variables implementation.

  • Richard Caseres for the awesome app icon he designed.