> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/blocks/python.md).

# Python

Run Python code in a block.

Python blocks run Python 3.11 code, with the packages in the block's [environment](/zerve-docs/environments/environments.md). They show their output directly under the code, as in a Jupyter notebook.

## Using results from other blocks

Variables created in a block are available to the blocks connected after it. You don't need to save or reload data between blocks. See [Variables, outputs and caching](/zerve-docs/notebooks/variables-outputs-and-caching.md).

## Imports

Imports in a block only apply to that block. To make an import available to every block, add it to [Global imports](/zerve-docs/notebooks/global-imports.md).

## Tidying code

Use **Lint code** in the block toolbar, or **Shift+Alt+L** (Windows) or **⇧+⌥+L** (Mac), to tidy a block's code. To tidy every block at once, use **Shift+Alt+Ctrl+L** or **⇧+⌥+⌘+L**.

## Running in parallel

To run a Python block many times in parallel, once for each item in a list, use [Fleet](/zerve-docs/compute/fleet.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/notebooks/blocks/python.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.