pythonnet / pythonnet/pythonnet
Isolate loaded assemblies inside an AssemblyLoadContext
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 780
- PR merge metrics
- No merged PRs in 30d
Description
When loading a .NET Framework runtime a new AppDomain is created and everything is loaded into that AppDomain. However, when using Core CLR this isn't possible and everything is loaded into the single AppDomain. Could we instead create a new AssemblyLoadContext and load all referenced assemblies into this in order to give some level of isolation between PythonNET and anything else that might be using .NET within the same process?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Investigate the Core CLR loading path and determine whether a dedicated AssemblyLoadContext can isolate PythonNET's referenced assemblies; define the isolation behavior and validation needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100