> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/documentation/en/framework/externals/projects/python.md).

# Python (python)

The capability scope, deployment products, integration entry points and usage boundaries of the Python project.

Python evaluation capabilities are provided through IronPython, suitable for using languages and libraries compatible with this runtime in controlled rules.

| Item                  | value                                                                         |
| --------------------- | ----------------------------------------------------------------------------- |
| source code directory | `externals/python`                                                            |
| main bag              | `Zongsoft.Externals.Python`                                                   |
| Companion theme       | [Scripts and Expressions](/documentation/en/framework/externals/scripting.md) |

## Deployment and Usage Portal

Append the main package to the existing host's [Deployment checklist](/documentation/en/references/deploy-files.md), and retain the plugin list, assembly and ancillary running resources in the package:

{% code title="Application.deploy (append fragment)" %}

```ini
[plugins zongsoft externals python]
nuget:Zongsoft.Externals.Python
```

{% endcode %}

Match expression evaluator by name `Python` after application initialization. The deployment must retain the required lib standard library and cannot rely on the system CPython package installation results.

## Integration Steps

1. Confirm that IronPython and the standard library are complete in the deployment directory.
2. Use the variable transfer method in the topic to verify simple expressions, and then verify the libraries actually imported by the application.
3. Establish clear execution boundaries for concurrent calls, input and output, and global state.

For specific configuration, calling examples and related basic concepts, see [Scripts and Expressions](/documentation/en/framework/externals/scripting.md).

## Project Boundaries

{% hint style="info" %}
💡 Currently implements a reuse engine and switches runtime IO during calls. The independent variable dictionary does not guarantee thread isolation; it is up to the application to serialize or use a separate process when needed, and the evaluator cannot be used as a security sandbox.
{% endhint %}

## Further Reading

[Browse extensions by project](/documentation/en/framework/externals/projects.md) · [Scripts and Expressions](/documentation/en/framework/externals/scripting.md) · [source code and project description](https://github.com/Zongsoft/framework/tree/main/externals/python)


---

# 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.zongsoft.com/documentation/en/framework/externals/projects/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.