ipybox 0.2.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- ipybox-0.2.0/LICENSE +202 -0
- ipybox-0.2.0/PKG-INFO +291 -0
- ipybox-0.2.0/README.md +268 -0
- ipybox-0.2.0/ipybox/__init__.py +3 -0
- ipybox-0.2.0/ipybox/__main__.py +95 -0
- ipybox-0.2.0/ipybox/config/default/dependencies.txt +0 -0
- ipybox-0.2.0/ipybox/config/default/environment.yml +6 -0
- ipybox-0.2.0/ipybox/config/default/pyproject.toml +15 -0
- ipybox-0.2.0/ipybox/container.py +126 -0
- ipybox-0.2.0/ipybox/docker/Dockerfile +43 -0
- ipybox-0.2.0/ipybox/executor.py +325 -0
- ipybox-0.2.0/ipybox/scripts/cleanup.sh +9 -0
- ipybox-0.2.0/ipybox/scripts/server.sh +5 -0
- ipybox-0.2.0/ipybox/utils.py +9 -0
- ipybox-0.2.0/pyproject.toml +54 -0
ipybox-0.2.0/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
ipybox-0.2.0/PKG-INFO
ADDED
|
@@ -0,0 +1,291 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: ipybox
|
|
3
|
+
Version: 0.2.0
|
|
4
|
+
Summary: Python code execution sandbox based on IPython and Docker
|
|
5
|
+
Home-page: https://github.com/gradion-ai/ipybox
|
|
6
|
+
License: Apache-2.0
|
|
7
|
+
Author: Martin Krasser
|
|
8
|
+
Author-email: martin@gradion.ai
|
|
9
|
+
Requires-Python: >=3.10,<3.13
|
|
10
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
15
|
+
Requires-Dist: aiodocker (>=0.23.0,<0.24.0)
|
|
16
|
+
Requires-Dist: aiofiles (>=24.1,<25.0)
|
|
17
|
+
Requires-Dist: aiohttp (>=3.10,<4.0)
|
|
18
|
+
Requires-Dist: pillow (>=11.0,<12.0)
|
|
19
|
+
Requires-Dist: tornado (>=6.4,<7.0)
|
|
20
|
+
Requires-Dist: typer (>=0.12.5,<0.13.0)
|
|
21
|
+
Description-Content-Type: text/markdown
|
|
22
|
+
|
|
23
|
+
# ipybox
|
|
24
|
+
|
|
25
|
+
A secure, lightweight Python code execution sandbox based on IPython and Docker, specifically designed for AI/ML applications and LLM agents.
|
|
26
|
+
|
|
27
|
+
<p align="center">
|
|
28
|
+
<img src="docs/logo.png" alt="logo">
|
|
29
|
+
</p>
|
|
30
|
+
|
|
31
|
+
## Overview
|
|
32
|
+
|
|
33
|
+
This project provides a sandboxed Python code execution environment built on IPython and Docker. It offers:
|
|
34
|
+
|
|
35
|
+
- **Secure Execution**: Code runs in Docker containers, preventing unauthorized system access
|
|
36
|
+
- **Flexible Dependencies**: Supports static and runtime dependency management
|
|
37
|
+
- **Real-time Streaming**: Chunked streaming of execution output as it's generated
|
|
38
|
+
- **Image Support**: Handle image outputs from matplotlib and other visualization libraries
|
|
39
|
+
- **Resource Control**: Container lifecycle management and built-in timeout mechanisms
|
|
40
|
+
- **Reproducible Environment**: Consistent execution environment across different systems
|
|
41
|
+
- **LLM Agent Ready**: Ideal for AI applications that need to execute Python code
|
|
42
|
+
|
|
43
|
+
This project is in early beta, with active development of new features ongoing.
|
|
44
|
+
|
|
45
|
+
## Installation
|
|
46
|
+
|
|
47
|
+
### Python package
|
|
48
|
+
|
|
49
|
+
```bash
|
|
50
|
+
pip install ipybox
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
### Container image
|
|
54
|
+
|
|
55
|
+
**Note**: Building the container image requires [Docker](https://www.docker.com/) to be installed. Containers will run with the same user and group IDs as the user who built the image, ensuring proper file permissions on mounted host directories.
|
|
56
|
+
|
|
57
|
+
#### Default build
|
|
58
|
+
|
|
59
|
+
To build a container image with default settings and no extra dependencies:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
python -m ipybox build
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
This creates a Docker image tagged as `gradion/ipybox` with base Python dependencies required for the code execution environment.
|
|
66
|
+
|
|
67
|
+
#### Custom build
|
|
68
|
+
|
|
69
|
+
To create a custom image with additional dependencies for your application, create a dependencies file (e.g., `dependencies.txt`) following. For example:
|
|
70
|
+
|
|
71
|
+
```txt
|
|
72
|
+
pandas = "^2.2"
|
|
73
|
+
scikit-learn = "^1.5"
|
|
74
|
+
matplotlib = "^3.9"
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
To build the image with custom tag and dependencies:
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
python -m ipybox build \
|
|
81
|
+
--tag my-box:v1 \
|
|
82
|
+
--dependencies path/to/dependencies.txt
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
The dependencies file should list Python packages in [Poetry dependency specification format](https://python-poetry.org/docs/dependency-specification/). These will be installed in addition to the base dependencies required for the execution environment. The execution container also supports [installing dependencies at runtime](#installing-dependencies-at-runtime).
|
|
86
|
+
|
|
87
|
+
## Usage
|
|
88
|
+
|
|
89
|
+
The following examples demonstrate how to use the `ExecutionContainer` and `ExecutionClient` context managers to execute Python code in an IPython environment running in a Docker container. Runnable scripts of the following code snippets are available in the [examples](examples/) directory.
|
|
90
|
+
|
|
91
|
+
### Basic usage
|
|
92
|
+
|
|
93
|
+
Here's a simple example that demonstrates how to execute Python code in an execution container. The `ExecutionContainer` context manager creates and starts a container for code execution, and the `ExecutionClient` context manager connects to an IPython kernel running in the container. The example below executes the code `print('Hello, world!')` and prints the output text:
|
|
94
|
+
|
|
95
|
+
```python
|
|
96
|
+
from gradion.executor import ExecutionContainer, ExecutionClient
|
|
97
|
+
|
|
98
|
+
# Create and start a container for code execution
|
|
99
|
+
async with ExecutionContainer(tag="gradion/executor") as container:
|
|
100
|
+
# Create and connect to an IPython kernel
|
|
101
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
102
|
+
# Execute Python code and await the result
|
|
103
|
+
result = await client.execute("print('Hello, world!')")
|
|
104
|
+
# Print the execution output text
|
|
105
|
+
print(f"Output: {result.text}") # Output: Hello, world!
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
The default image used by `ExecutionContainer` is `gradion/executor`. You can specify a custom image with the `tag` argument like in `ExecutionContainer(tag="my-box:v1")`, for example.
|
|
109
|
+
|
|
110
|
+
### State management
|
|
111
|
+
|
|
112
|
+
Code execution within the same client context is stateful i.e. you can reference variables from previous executions. Code executions in different client contexts are isolated from each other:
|
|
113
|
+
|
|
114
|
+
```python
|
|
115
|
+
async with ExecutionContainer() as container:
|
|
116
|
+
async with ExecutionClient(host="localhost", port=container.port) as client_1:
|
|
117
|
+
# Execute code that defines variable x
|
|
118
|
+
result = await client_1.execute("x = 1")
|
|
119
|
+
assert result.text is None
|
|
120
|
+
|
|
121
|
+
# Reference variable x defined in previous execution
|
|
122
|
+
result = await client_1.execute("print(x)")
|
|
123
|
+
assert result.text == "1"
|
|
124
|
+
|
|
125
|
+
async with ExecutionClient(host="localhost", port=container.port) as client_2:
|
|
126
|
+
# Variable x is not defined in this client context
|
|
127
|
+
try:
|
|
128
|
+
await client_2.execute("print(x)")
|
|
129
|
+
except ExecutionError as e:
|
|
130
|
+
assert e.args[0] == "NameError: name 'x' is not defined"
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
### Output streaming
|
|
134
|
+
|
|
135
|
+
The execution client supports streaming output as it's generated during code execution:
|
|
136
|
+
|
|
137
|
+
```python
|
|
138
|
+
async with ExecutionContainer() as container:
|
|
139
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
140
|
+
# Code that produces output gradually
|
|
141
|
+
code = """
|
|
142
|
+
import time
|
|
143
|
+
for i in range(5):
|
|
144
|
+
print(f"Processing step {i}")
|
|
145
|
+
time.sleep(1)
|
|
146
|
+
"""
|
|
147
|
+
|
|
148
|
+
# Submit the execution and stream the output
|
|
149
|
+
execution = await client.submit(code)
|
|
150
|
+
async for chunk in execution.stream():
|
|
151
|
+
# Output will be printed gradually:
|
|
152
|
+
print(f"Received output: {chunk}")
|
|
153
|
+
# Received output: Processing step 0
|
|
154
|
+
# Received output: Processing step 1
|
|
155
|
+
# Received output: Processing step 2
|
|
156
|
+
# Received output: Processing step 3
|
|
157
|
+
# Received output: Processing step 4
|
|
158
|
+
|
|
159
|
+
# Get the aggregated result
|
|
160
|
+
result = await execution.result()
|
|
161
|
+
# Print the aggregated output text
|
|
162
|
+
print(f"Aggregated output:\n{result.text}")
|
|
163
|
+
# Aggregated output:
|
|
164
|
+
# Processing step 0
|
|
165
|
+
# Processing step 1
|
|
166
|
+
# Processing step 2
|
|
167
|
+
# Processing step 3
|
|
168
|
+
# Processing step 4
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
The `stream()` method accepts an optional `timeout` argument (defaults to 120 seconds). In case of timeout, the execution is automatically terminated by interrupting the kernel.
|
|
172
|
+
|
|
173
|
+
### Installing dependencies at runtime
|
|
174
|
+
|
|
175
|
+
```python
|
|
176
|
+
async with ExecutionContainer() as container:
|
|
177
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
178
|
+
# Install the einops package
|
|
179
|
+
await client.execute("!pip install einops")
|
|
180
|
+
# Then you can use it in the following code
|
|
181
|
+
# execution within the same client context
|
|
182
|
+
result = await client.execute("""
|
|
183
|
+
import einops
|
|
184
|
+
print(einops.__version__)
|
|
185
|
+
""")
|
|
186
|
+
print(f"Output: {result.text}") # Output: 0.8.0
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
### Creating and returning plots
|
|
190
|
+
|
|
191
|
+
Plots created with `matplotlib` or other libraries are returned as PIL images:
|
|
192
|
+
|
|
193
|
+
```python
|
|
194
|
+
async with ExecutionContainer() as container:
|
|
195
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
196
|
+
execution = await client.submit("""
|
|
197
|
+
!pip install matplotlib
|
|
198
|
+
|
|
199
|
+
import matplotlib.pyplot as plt
|
|
200
|
+
import numpy as np
|
|
201
|
+
import time
|
|
202
|
+
|
|
203
|
+
x = np.linspace(0, 10, 100)
|
|
204
|
+
plt.figure(figsize=(8, 6))
|
|
205
|
+
plt.plot(x, np.sin(x))
|
|
206
|
+
plt.title('Sine Wave')
|
|
207
|
+
plt.show()
|
|
208
|
+
|
|
209
|
+
print("Plot generation complete!")
|
|
210
|
+
""")
|
|
211
|
+
|
|
212
|
+
# Stream the output text as it's generated
|
|
213
|
+
async for chunk in execution.stream():
|
|
214
|
+
print(chunk, end="", flush=True)
|
|
215
|
+
|
|
216
|
+
# Obtain the execution result
|
|
217
|
+
result = await execution.result()
|
|
218
|
+
assert "Plot generation complete!" in result.text
|
|
219
|
+
|
|
220
|
+
# Get created PIL image from the result
|
|
221
|
+
result.images[0].save(f"output.png")
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
Images are not part of the output stream, but are available as a `images` list in the `result` object. The example above saves the created image as [output.png](docs/sine.png):
|
|
225
|
+
|
|
226
|
+
### Bind mounts
|
|
227
|
+
|
|
228
|
+
You can mount host directories into the container to allow code execution to access external files:
|
|
229
|
+
|
|
230
|
+
```python
|
|
231
|
+
# Map host paths to container paths. Host paths can be absolute or relative.
|
|
232
|
+
# Container paths must be relative and are created as subdirectories of the
|
|
233
|
+
# /app directory in the container. The /app directory is the container's
|
|
234
|
+
# working directory.
|
|
235
|
+
binds = {
|
|
236
|
+
"./data": "data", # Read data from host
|
|
237
|
+
"./output": "output" # Write results to host
|
|
238
|
+
}
|
|
239
|
+
|
|
240
|
+
# Create a data file on the host
|
|
241
|
+
async with aiofiles.open("data/input.txt", "w") as f:
|
|
242
|
+
await f.write("hello world")
|
|
243
|
+
|
|
244
|
+
async with ExecutionContainer(binds=binds) as container:
|
|
245
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
246
|
+
# Read from mounted data directory
|
|
247
|
+
result = await client.execute("""
|
|
248
|
+
with open('data/input.txt') as f:
|
|
249
|
+
data = f.read()
|
|
250
|
+
|
|
251
|
+
# Process data...
|
|
252
|
+
processed = data.upper()
|
|
253
|
+
|
|
254
|
+
# Write to mounted output directory
|
|
255
|
+
with open('output/result.txt', 'w') as f:
|
|
256
|
+
f.write(processed)
|
|
257
|
+
""")
|
|
258
|
+
|
|
259
|
+
# Check the result file on the host
|
|
260
|
+
async with aiofiles.open("output/result.txt", "r") as f:
|
|
261
|
+
assert await f.read() == "HELLO WORLD"
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
### Environment variables
|
|
265
|
+
|
|
266
|
+
Environment variables can be passed to the container for configuration or secrets:
|
|
267
|
+
|
|
268
|
+
```python
|
|
269
|
+
env = {
|
|
270
|
+
"API_KEY": "secret-key-123",
|
|
271
|
+
"DEBUG": "1"
|
|
272
|
+
}
|
|
273
|
+
|
|
274
|
+
async with ExecutionContainer(env=env) as container:
|
|
275
|
+
async with ExecutionClient(host="localhost", port=container.port) as client:
|
|
276
|
+
# Access environment variables in executed code
|
|
277
|
+
result = await client.execute("""
|
|
278
|
+
import os
|
|
279
|
+
|
|
280
|
+
api_key = os.environ['API_KEY']
|
|
281
|
+
print(f"Using API key: {api_key}")
|
|
282
|
+
|
|
283
|
+
debug = bool(int(os.environ.get('DEBUG', '0')))
|
|
284
|
+
if debug:
|
|
285
|
+
print("Debug mode enabled")
|
|
286
|
+
""")
|
|
287
|
+
print(result.text)
|
|
288
|
+
# Using API key: secret-key-123
|
|
289
|
+
# Debug mode enabled
|
|
290
|
+
```
|
|
291
|
+
|