The maintainers of the Spring Framework for Python ( Spring Python ) wonder how much of a priority it is to have compatibility with platforms other than CPython. In other words, should they support IronPython and Jython - and if so what should they do about their C extension dependencies? This question sparks a good discussion and is relevant to many other Python projects and applications: Need for supporting IronPython, Jython? " One of the topics on my mind recently, as we consider refactoring the core container, is how we ensure that when we introduce internal dependencies, such as possibly the Amara libraries for XML processing, what secondary constraints we might be introducing. " " For example, Amara represents a very pythonic and therefore simple to read and use approach to developing XML processing, such as our very own XML application configuration parsers. So from that perspective, things are very attractive. But then you ask the question, "can I run this
Thanks for the reference. Just to clarify, my comment about IronPython was tangential for my poste and only in reply to Eric Lippert who mentioned it as addressing my concerns about Microsoft's process and release cycle compared to open-source, and also in relation to an occupational developer's needs. I am actually very interested in IronPython, but I don't think it hosted in Visual Studio is what the occupational (aka "occasional") programmer really needs, at least not at this juncture, and I don't think it's existence means that Microsoft's 3 year release cycle is now okay, which was the original purpose of my rant.
ReplyDelete