I love Python.Included! Recently updated from 3.13.1 to 3.13.2 for no reason just out of curiosity and noticed that InstallPip fails.
The root cause seems to be in the dependecy Python.Deployment 2.0.5 (file version 1.5):
InstallPip has no arguments there, but Python.Included calls it with CancellationToken as argument.
No issues when running from source code. The problem is definitely in the nuget package only.
There is something else that I don't understand: Even though InstallPip returns a Task, I still need to wrap it around Task.Run(async () => await Installer.InstallPip().ConfigureAwait(false)); to avoid deadlocks.
I love Python.Included! Recently updated from 3.13.1 to 3.13.2 for no reason just out of curiosity and noticed that InstallPip fails.
The root cause seems to be in the dependecy Python.Deployment 2.0.5 (file version 1.5):
InstallPip has no arguments there, but Python.Included calls it with CancellationToken as argument.
No issues when running from source code. The problem is definitely in the nuget package only.
There is something else that I don't understand: Even though InstallPip returns a Task, I still need to wrap it around Task.Run(async () => await Installer.InstallPip().ConfigureAwait(false)); to avoid deadlocks.