From: "Peter J. Holzer" <hjp-pyt...@hjp.at>
--prnws536gtytpj5v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-06-22 17:20:29 -0700, denis.akhiya...@gmail.com 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 --=20 _ | Peter J. Holzer | we build much bigger, better disasters now |_|_) | | because we have much more sophisticated | | | h...@hjp.at | management tools. __/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/> --prnws536gtytpj5v Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAlsuAsMACgkQ8g5IURL+ KF3tZRAArjij8tON0JDZA9HW2eC3hjLEQVR5xk8qvsKOsuLfSZ4vpzF9DyAq+mSy R+poIBfJwQglBeHs3yMOhxzsynZHD8sdoO6BtdAAZHNlgl8aCAzRQqxxJxOSi9RY A0VfL1IGt8M7FiT//nttpxGKknSaDVNy37H/fPSertJOD7QIvh7OjOD1wpnfFpg7 JO4B5Q1R4J2HBVwqszcsJgoBJtQLTKg4peZVqyLrKZeF6nr8YyPmtx4pHLGLYTtX gH1K25dERjWpv0soISd0GI6aCJvr7Pmm6OmxNK8Qw+wB1maDxAkI/tVCs3HZRIsf q6BW+mWC/WCmNJg+A8QenC8ISp/pBhOaM3WIln0g/FcWEfOOwut9vnQJcyLrFYYW GXTHhVpJQm5KwcfTTEXh5Czorr6bfIa9IvTOnhZukgRdc0lSDT2JMykmeo97bS9M rC6GJqk0qVEVw66+M0vbVmaKbzugqH0rsYSGoHiTaAYFyFuq5T+G8etl8phGmpXN sRw9jRzBj5eoA3toYK4XDRB7hm8JzQjCxJdSjoP3hgmqa7jmozor70pm22nUy8ql e7ZE9E3cuUyKLe1zAfZ07W8dUo1WcNB9h0zedR53jx29m5W/ouixGZ1VhQN6DcRY XUYAR66l1Xk4AZxXrKWmYAfxlC2PION/oHykev2nR5sCgFrF1Xw= =dC9K -----END PGP SIGNATURE----- --prnws536gtytpj5v-- --- BBBS/Li6 v4.10 Toy-3 * Origin: Prism bbs (1:261/38) -- https://mail.python.org/mailman/listinfo/python-list