In this blog entry Dave Fugate (IronPython tester and infrastructure guy for Microsoft) explains the current state of VS support for Python and as Visual Studio 2010 approaches he looks to the future...
I think I speak for everyone on the IronPython Team when I say we’d love to see IronPython support in Visual Studio by default without the need for any language service addition. The thing is these types of decisions are made at a much higher level than us and are heavily influenced by business needs. What I’m getting at here is if enough people provided feedback via the proper channels that:If you're looking for an IDE for working with IronPython the best option currently is probably SharpDevelop, which has great IronPython integration.
then the next version of VS could very well have Python support built into it. What are the proper channels for feedback you ask? The VS 2010 feedback page would be a great start.
- The next version of VS is great, but it’d be better if it supported Python development
- You don’t currently use VS but you would if it had Python support
- Ahem…you’d be willing to pay for IronPython support in VS