Workspace dependencies

When a task needs to build or edit a Word, Excel or PowerPoint file, DataMind Oda works from a runtime of its own on your computer: a copy of Python with the libraries document work needs, plus Node.js and pnpm when the copy provides them. This page explains what the runtime contains, where it lives and how it stays current. The document workflow itself is on Create Word, Excel and PowerPoint files.

What the runtime contains

The Office skills behind document work run on this runtime, not on software already installed on your computer.

• Oda's own copy of Python, with the libraries document work uses: numpy, pandas, python-docx, python-pptx, openpyxl, Pillow, lxml and XlsxWriter.
• Node.js and pnpm when the copy provides them.
• No PDF library and no plotting library. Charts inside a document are the file's own charts.

The runtime leaves your own setup alone:

• Nothing is added to your own Python or packages, and the runtime never changes PATH or your package-manager settings.
• Preparing the runtime copies files that came with DataMind Oda, so nothing is downloaded.
• The task receives absolute paths into the prepared copy, so a script always finds Oda's copy of Python and its libraries.

The step in the chat

When a chat first needs the runtime for document work, Oda prepares it and the chat shows a step called Load workspace dependencies. The step returns the paths into the copy, and the task continues from there.

• Oda keeps one prepared copy on your computer, and every chat that does document work uses it.
• Depending on how DataMind Oda is set up, the copy is used where it is kept, or the first use places it in Oda's own storage for your user. Either way it stays on your computer.
• Repeated preparation calls return the same paths; the copy is not rebuilt for each task.

Reuse and updates

• While the copy stays the same, Oda reuses it, and packages added to it are kept.
• When the runtime changes, Oda prepares the new copy beside the current one and switches to it in a single step, so a task never meets a half-prepared runtime.
• If a switch is blocked, Oda falls back safely: the previous complete copy stays in service for one more task, and the next attempt tries again. On Windows, a switch blocked by a file in use is retried for about ten seconds first.

Questions, answered

When does Oda prepare the runtime?

The first time a chat needs it for document work; the chat then shows the step Load workspace dependencies. Later document tasks reuse the prepared copy.

Where does Oda keep the runtime?

On your computer. Oda keeps one prepared copy; depending on how DataMind Oda is set up, it is used where it is kept or placed into Oda's own storage for your user on first use. It never goes into your own Python setup or your PATH.

Does preparing the runtime download anything?

No. The files come with DataMind Oda, and preparing the runtime copies them on your computer, so nothing is downloaded.

Which libraries does the runtime include?

Oda's copy of Python includes numpy, pandas, python-docx, python-pptx, openpyxl, Pillow, lxml and XlsxWriter. Node.js and pnpm are part of the runtime when the copy provides them. It does not include a PDF library or a plotting library; charts in a document are the file's own charts.

Does every chat prepare its own copy?

No. There is one prepared copy on the computer, and every chat that does document work uses it; the paths Oda hands to a task point into that copy.

Can packages be added to the runtime?

Yes. Packages added to the prepared copy are kept when Oda reuses it.

What happens to the runtime when DataMind Oda updates?

While the runtime stays the same, Oda reuses the prepared copy and keeps the packages added to it. When the runtime changes, Oda prepares the new copy and switches to it in one step; if the switch cannot complete, the previous complete copy stays in service for one more task and the next attempt tries again.

Does the runtime differ between computers?

Yes. Oda prepares the copy that fits your computer's platform and architecture, and a copy that does not fit the computer is refused rather than used.