You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, we should not expose the Runtime class. All functionality that is of use outside of the implementation of Python.NET itself should instead be moved to separate (public) classes.
Actually as an embedder, I'd love/need to have the Runtime internals exposed.
So much so I had to build python.net myself and add the 'friend' attribute: [assembly: InternalsVisibleTo("my assembly")]
I see the need for embedding python over the need to import the clr in python.
Maybe there should be a target/build for embedding?
@quickwire although it might be advantageous to have direct access to C routines, Python.NET provides a higher-level product. Because of that, we should hide the implementation details as much as possible to be able to change it later at any moment. Also see my comment on your thread state issue.
Activity
bmiller-pm commentedon Sep 2, 2020
Actually as an embedder, I'd love/need to have the Runtime internals exposed.
So much so I had to build python.net myself and add the 'friend' attribute:
[assembly: InternalsVisibleTo("my assembly")]I see the need for embedding python over the need to import the clr in python.
Maybe there should be a target/build for embedding?
lostmsu commentedon Sep 2, 2020
@quickwire although it might be advantageous to have direct access to C routines, Python.NET provides a higher-level product. Because of that, we should hide the implementation details as much as possible to be able to change it later at any moment. Also see my comment on your thread state issue.