Victor
Victor
@filmor we could consider separating .NET build and Python build. Then Python build would only need to download `Python.Runtime.dll` or extract it from downloaded NuGet package.
Removing this from 3.0.0 milestone. @filmor if you are actively working on it - readd. Because this is not a breaking change there's no harm in releasing it with 3.0.1...
Also, to officially support 32 bit we need it in CI.
@filmor have you tried with .NET Core? If the behavior is different, I would simply open a bug in Mono.
Python.NET 2.x permits all sorts of conversions in attempts to match the function arguments, some of which permit data loss. Please, try 3.0 previews of Python.NET. I believe 3.0 will...
Shallow googling did not show any supported way to load .winmd files at runtime with .NET variants :(
As a workaround you can try to add Windows.winmd reference to a custom build of Python.Runtime.
Another workaround is to create a library, that directly references winmd file, and have a public `Create` method, that instantiates the necessary class for you. Touching any class there might...
@Meisterrichter offtopic idea: if you want your .NET app run within a virtualenv, can you maybe launch it from Python executable? E.g. do ```python # TODO: setup clr first import...
Oracle Cloud free tier includes free ARM64 instances https://www.oracle.com/cloud/free/