Personally, I consider python (CPython) and IronPython as different flavors of the same language. Python has a near ubiquitous presence on all platforms and has access to an enormous library of add-ons. IronPython makes accessing the .Net world seamless and opens up access to the enormous .Net Framework libraries and third-party assemblies. I can take my pythonic skills from one environment to the other, much the same way I can take my C or C++ skills from one compiler/OS to another.
The python.net plug-in for CPython provides much of the access to .Net but it is not as seamless as IronPython and definitely not as fast. But it is a useful tool for writing python code that must run in CPython and IronPython while still providing access to .Net assemblies. IronPython is growing in functionality all the time and it won't be long before it can seamlessly support third-party DLLs of compiled code. So the two worlds of CPython and IronPython are converging, building on the common ground that is the python language. Is one better than the other? Like any choice of language, it all depends on what you need to accomplish. From: [email protected] [mailto:[email protected]] On Behalf Of Hank Fay Sent: Tuesday, May 18, 2010 11:11 AM To: Discussion of IronPython Subject: [IronPython] .Net attributes/decorators In reviewing the discussion of .Net decorators in the list (thank you Google Groups), I did not come across a discussion of what I saw as the central issue: is IronPython to be a Superset of Python (every Python program will run in IronPython, not every IronPython program will run in Python), or is IronPython to be an equivalent set (every Python program will run in IPy, and every IPy will run in Python). Has there been a discernment on this issue? For me, coming from a non-Python world, it makes sense to view IPy as a superset of Python. This perspective would, e.g., allow the use of .Net decorators on classes (which in turn would facilitate returning .Net objects). I've read about the ways of using __clrtype__ to do this in a Pythonic manner. My interest is in simplicity and clarity in my programs, rather than maintaining two-way compatibility (which I could not port to Python, in any case, for a .Net program using .Net features). thanks, Hank Fay
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
