Replies: 2 comments
-
Hi @Antropath, thank you for your feedback! I wasn't aware of alternatives, thus the starting of our own local executor. Now we probably need to keep it inside as it's practical to do quick changes to it. But you're welcome to fork/copy it elsewhere! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Antropath if you're looking for a similar package for sandboxing python code you might be interested in checking https://github.com/zopefoundation/RestrictedPython |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Thanks for your great work. I have 2 questions/suggestions:
Separate python package: I was wondering if you have ever considered splitting out the local code execution module into a small, separate python package? This could be reused also in other frameworks - or with even simpler, but more specialized code agent implementations. I don't think there is any great alternative around (see question 2)
Alternatives: Are you aware of any other tools that allow similar fine-grained control of local execution? If yes, why were they not used? Have you considered using Docker as an alternative? It's for sure slower, but allows isolation on the system level, which ultimately provides more freedom.
Keen to get your insights and happy to collaborate on this if it comes to that.
Beta Was this translation helpful? Give feedback.
All reactions