ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
Bonus materials, exercises, and example projects for our Python tutorials
EducationJupyter Notebook · HTMLGitHub @realpythonSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Bonus materials, exercises, and example projects for Real Python's Python tutorials.
The best way to get support for Real Python courses, articles, and code in this repository is to join one of our weekly Office Hours calls or to ask your question in the RP Community Chat.
Due to time constraints, we cannot provide 1:1 support via GitHub. See you on Slack or on the next Office Hours call 🙂
We use Ruff to ensure a consistent code style and formatting for all of our sample code in this repository.
Run the following commands to validate your code against the linters:
$ ruff format --check
$ ruff check
Make sure you're using the exact Ruff version specified in requirements.txt.
Ruff can automatically ensure a consistent code formatting in this repository. On CI, it runs in "check" mode to ensure any new files added to the repo follow PEP 8. If you see linter warnings that say something like "would reformat some_file.py", then it means that Ruff disagrees with your formatting.
The easiest way to resolve these errors is to run Ruff locally on the code and then commit those changes, as explained below.
To automatically reformat your code to be consistent with our code style guidelines, run Ruff in the repository root folder:
$ ruff format
$ ruff check --fix