What does HackerNews think of pythonnet?

Python for .NET is a package that gives Python programmers nearly seamless integration with the .NET Common Language Runtime (CLR) and provides a powerful application scripting tool for .NET developers.

Language: C#

#13 in C#
#12 in .NET
#159 in Hacktoberfest
#124 in Python
And TensorFlow for C# is alive and kicking: https://losttech.software/gradient.html

I guess this is sort of an ad.

Swift was a weird choice for statically typed TensorFlow, being only popular on the platform, that does not have GPU/TPU support in TensorFlow, which is, basically, a requirement for any serious work. The fact, that they had to fork the compiler did not help either.

TensorFlow for C# is much like TensorFlow for Swift. There's a statically typed binding to the core types with the rest of the TensorFlow API available through an open source Python.NET project [1]. Unlike Swift version though, that second part is also mostly statically typed, so you can get IDE autocompletion hints. Also, .NET runtime has native support for dynamic languages.

Like with Swift for TensorFlow, we ported all recent interesting neural network architectures (and maybe even more): Transformers (GPT-2) [2], CNNs (YOLOv4) [3], Q-learning (e.g. RL, actor-critic) [4], and even some cool ones, that have lots of unexplored potential like Siren [5] (this one uses sin/cos as activation functions).

Although we have not worked on automatic differentiation yet, unlike Swift, it will not need compiler support. .NET (and Java) can inspect and generate code at runtime, so autodiff can be implemented in a library.

We also have integration with Unity ML Agents for training robotic agents [4].

[1] https://github.com/pythonnet/pythonnet/

[2] https://github.com/losttech/Gradient-Samples/tree/master/GPT...

[3] https://github.com/losttech/YOLOv4

[4] https://github.com/losttech/Gradient-Samples/tree/master/RL-...

[5] https://github.com/losttech/Siren https://vsitzmann.github.io/siren/

I'm not disputing that IronPython can be useful (although one also has to consider https://github.com/pythonnet/pythonnet, which wraps CPython into an IronPython-like projection). But if it can't share the library ecosystem, it might as well be a different language for all practical purposes. And it turned out that there aren't enough people who were interested in a Python/.NET combo for its own sake, so it remained niche. Any new implementation of Python on top of .NET VM would likely get similar reception for all the same reasons.
There is a similar project for .NET: https://github.com/pythonnet/pythonnet

It makes calling C# as easy as:

  import clr
  import System
  uri = System.Uri('http://python.org')
And also works the other way around. In both cases you have to mind GIL though.
Plus, now you have Python for .NET[0] and similar projects that allow you to seamlessly integrate CPython into your .NET program. This gives you the best of both worlds and negates a lot of the value of a dedicated .NET Python implementation.

[0]: https://github.com/pythonnet/pythonnet