2 ms·
True, IronPython3 isn't ready and with 2.7 EOL I would say that it may not be a great fit for someone currently weighing up their options between it and pythonn
by shbooms 7y ago
True, IronPython3 isn't ready and with 2.7 EOL I would say that it may not be a great fit for someone currently weighing up their options between it and pythonnet to use in a current project.
Development on IP3 is, however, still very alive and active so I wouldn't consider the entire project dead:
https://github.com/IronLanguages/ironpython3/commits/master https://github.com/IronLanguages/ironpython3/commits/master