There are two major modes of using Python.NET:

1. Embedding Python into .NET
2. Embedding .NET into Python

Each of them has a distinct "support" status for .NET Core.

The first case should already be possible, as Python.NET can be compiled as a .NET Standard DLL that can be referenced within .NET Core.

The second case is actively being worked at in #857, I'll open a corresponding PR this weekend. There is a previous attempt in #612 that uses the older (in fact second) coreclr hosting API and significantly complicates the build-process, which is already annoyingly complicated.

Furthermore, we have to simplify the way how libpython is loaded in the embedding case, which @lostmsu has already tried out and we'll look into further once the new loading mechanism has landed.