luxferre/t-deckard
1
0
Fork 0
Code Actions Activity

tdeckboot vs autoexec notice

Browse Source
This commit is contained in:
Luxferre
2025-12-25 15:58:37 +02:00
parent c8e908d07b
commit 4fdd29cb55
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8
View File
@@ -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. 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? ### Is there any feature roadmap for core components?
The foundational module set is going to at least include high-level capabilities for: The foundational module set is going to at least include high-level capabilities for: