From 4fdd29cb556e5cfe4734ef3039ed747ab0ae6104 Mon Sep 17 00:00:00 2001 From: Luxferre Date: Thu, 25 Dec 2025 15:58:37 +0200 Subject: [PATCH] tdeckboot vs autoexec notice --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index baa29e5..0ebd034 100644 --- a/README.md +++ b/README.md @@ -273,6 +273,14 @@ It has been renamed. Place your startup code into `autoexec.py` instead. You can start it with `from tdeckboot import *` to give it the same extended capabilities as the interactive REPL. +### So, what's the difference between `tdeckboot.py` and `autoexec.py`? + +Everything that gets imported inside `tdeckboot.py` becomes automatically available in the T-DeckARD interactive REPL. This file is solely designed for passthrough import of modules into the REPL and nothing more. + +Everything that gets imported inside `autoexec.py` stays in `autoexec.py`. This is just your usual startup script. + +You can use `tdeckboot.py` for autoexecing but that's not recommended as this carries a heavy risk of REPL namespace pollution. + ### Is there any feature roadmap for core components? The foundational module set is going to at least include high-level capabilities for: