I am giving Microsoft some room for redemption for many mistakes made in the Ballmer era.
This support for Python in VS may be a step in that direction.
Agreed. Clearly I'm being unfair, but I think I may not be alone in my aversion to the old Ballmer brands. Perhaps SN should "do an Edge" on the VS moniker.
I don't think this has much to do with the change of the guard at the top. Iron Python was started in 2008, and Python tools for VS was first released in 2011.