[APIView] Epic: Remove Python sandboxing?
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
There are a number of issues related to the sandboxing environment the Python parser runs in. My understanding from @praveenkuttappan is that this was something we had tried a while ago and thought to apply more broadly to other languages. However, since then, the benefits have not proven to outweigh the costs.
So this issue serves two purposes:
1) to track the other issues we would resolve by removing sandboxing entirely for Python
2) to ask the question--_should_ we remove sandboxing for Python from APIView to simplify the architecture?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating APIView's Python parser sandbox and reviewing the related sandboxing issues; completion would require an architectural decision and resolution of the tracked follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100