Clarify usage of startup.sh in AGENTS.md documentation

Updated the instructions to emphasize that after invoking `./startup.sh`, users should not run `python scripts/<script>.py` directly, as it will lead to import errors. Removed outdated example and reinforced the importance of the `startup.sh` wrapper for module execution.
This commit is contained in:
thePR0M3TH3AN committed 2025-05-31 10:17:49 -04:00
1 parent d97da458dc
commit 738bc3dea8
1 file changed
+1 -6
+1 -6
View File
@@ -13,12 +13,7 @@
* Running a script this way ensures that `import scripts.common` (and other `scripts.*` imports) resolve correctly. * Running a script this way ensures that `import scripts.common` (and other `scripts.*` imports) resolve correctly.
* If you ever need to call a different script, still invoke it under `./startup.sh`, for example: * **Do not** follow a `./startup.sh` invocation by running `python scripts/<script>.py` on the next line. The `startup.sh` wrapper already executed the module; any additional direct invocation will fail because Python will not find the `scripts` package in that context.
```bash
# Custom-chart example:
./startup.sh python -m scripts.custom_chart --series UNRATE DCOILWTICO --start 2000-01-01 --end 2020-12-31
```
* **Never** call `refresh_data.py` from within a Task Command. This environment has **no internet access**, so attempts to fetch external data will fail. Data in `data/fred.db` must already be present. If you need to refresh data, run it only in an internet-connected shell: * **Never** call `refresh_data.py` from within a Task Command. This environment has **no internet access**, so attempts to fetch external data will fail. Data in `data/fred.db` must already be present. If you need to refresh data, run it only in an internet-connected shell: