On 2018-06-22 17:20:29 -0700, [email protected] wrote: > Either wait for IronPython 3.6, use COM interop, pythonnet, > subprocess, or things like gRPC. Based on PyPy experience, it is > probably 1-2 years of sponsored development to get a working > IronPython 3.6.
What is the current state of IronPython 3? The website is very
uninformative (there's a 4 year old blog post saying "we started a
repository", but that's it). The repository gets commits every now and
then (so it's obviously not dead yet), but neither the readme nor the
wiki give a hint beyond "not ready yet".
hp
--
_ | Peter J. Holzer | we build much bigger, better disasters now
|_|_) | | because we have much more sophisticated
| | | [email protected] | management tools.
__/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>
signature.asc
Description: PGP signature
-- https://mail.python.org/mailman/listinfo/python-list
