I'm fairly confident about MS's lukewarm support of IronPython. I don't think it will get more support, nor do I think it will get less support.

Interestingly, there is what looks like a pretty good IronRuby IDE that works in VS2008 created by a 3rd party. If IronPython had the equivalent, I think it would open up the market.

For me, the .Net ecology (WCF, WPF, Silverlight 4) is too good a thing to pass up. But if you don't need it, then yes, you will be a lot of stability sticking with Python.

Good luck.

Hank

>Thank you for the persistent information flow on your both the defunct VFP.net and your specific projects (we share the sames views on MS attitude vs interpreters à la Fox) and setting up this informative thread.
>
>Currently reviewing the coding of a rich-UI application à la Fox (not data-based though, hence not really a Dabo project). At this moment I do not trust MS enough to run an Ironpython-based project.
>
>Just sure about one thing - python for coding. The stability of the language is a joy.
>
>Started the non-UI part of an application with a view to later develop the UI within QT, WX or Ironpython. Depending on outcome of current debates within the python community and prospects of the various solutions.
>
>>I'm not putting down the knowledge you got from hand-coding subclasses. It's all useful stuff for certain tasks. My perspective is simply that those certain tasks for which it is useful should fall outside the realm of everyday business programming, because they clearly aren't necessary for it (as anyone who has created line-of-business apps in VFP can attest). In fact, that level of knowledge isn't needed to write frameworks with which to write business apps. Well, it would be needed if one where writing the framework in .Net, but that's the point.
>
>Well put.