How serverless, pipelines, classic jobs and bundles each get their Python libraries.
From Ultra Transcenders DBX-DEP by Tony Rough (coming December 2026)
This table is the core of the chapter. Find the runtime first, and only then choose the mechanism, because several of them work in only one place. Figure 2.1 shows the main routes, including the key a bundle uses for each.
| Environment | Declare libraries in | Init scripts | Python restart | JVM libraries |
|---|---|---|---|---|
| Serverless notebook | Environment side pane, %pip, base environment |
No | Apply restarts Python | No JAR libraries in notebooks |
| Serverless job task | Job environment spec (environments, environment_key) |
No | Installed before code runs | JAR dependencies on JAR tasks |
| Serverless pipeline | Pipeline environment |
No | restartPython() not supported |
Not supported |
| Classic pipeline | Pipeline environment |
Yes, not recommended | restartPython() not supported |
Not supported, even by init script |
| Classic, Cluster libraries mode | Compute-scoped libraries, Dependent libraries, %pip |
Yes, not recommended | restartPython() supported |
Maven and JARs, allowlisted in standard mode |
| Classic, Environments mode (Beta) | Base environment, job environment spec | No | Apply restarts Python | Spark JAR tasks not supported |
A bundle has two distinct places to declare a job task’s Python dependencies, and which applies depends on the compute.
```yaml
This note is one section of Ultra Transcenders DBX-DEP: Databricks Data Engineer Professional, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to the Databricks documentation.
Due on Amazon in December 2026, in Kindle and paperback editions.
About the book · DBX-DEP terms in the glossary · All DBX-DEP study notes
Which compute fits each kind of workload, and the constraint that forces a move away from serverless.
What a checkpoint holds and which query changes survive a restart.
How latency, cost and refresh decide between the two pipeline dataset types.
What each expectation action does to a bad record, and how quarantine is built.
When each table layout fits, and what existing tables need.
How grants flow down from catalogs and schemas, and where they stop.
The steps that really remove a person's data, and why they can't run back to back.