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
翻译准备中
教育Jupyter Notebook · HTMLGitHub @realpython自行安装运营者未确认
试用过了吗? 点一下就好,无需登录。
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
安装型项目无需部署域名也可验证。个人仓库可通过 GitHub 登录验证,组织仓库可使用上方的仓库验证文件。
制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 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