[IronPython] Python Tools for Visual Studio now accepting contributions

Jeff Hardy jdhardy at gmail.com
Wed May 11 22:39:17 CEST 2011


The IronPython Tools (or "old" tools) are the original VS integration
tools, developed when IronPython was still funded by MS. PTVS is a new
set of Python (not IronPython-specific; they support CPython and
IronPython, and some Jython and PyPy) tools Dino's working on for MS's
Technical Computing group. Some of the features are HPC-specific (like
MPI cluster debugging) but for the most part it's just a nice Python
environment, and a lot more stable than the old tools.

Dino, can the HPC stuff be split out for people who don't need it?

PTVS is significantly better then the old tools and is also under
active development, and now that they're accepting contributions it
makes sense to me to retire the old tools and just get people to
download PTVS (I doubt we'll bundle them, but instead have a big link
next on the download page).

- Jeff

On Wed, May 11, 2011 at 1:27 PM, Keith Rome <rome at wintellect.com> wrote:
> Please forgive my ignorance on this matter (I don't currently use any of the integrated VS functionality - have been working with embedding the runtime in an existing application), but what is the difference between "IronPython Tools" and "Python Tools for Visual Studio"? I was under the impression this was the same thing?
>
>
> Keith Rome
> Senior Consultant and Architect
> MCPD-EAD, MCSD, MCDBA, MCTS-WPF, MCTS-TFS, MCTS-WSS
> Wintellect | 770.617.4016 | krome at wintellect.com
> www.wintellect.com
>
> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dino Viehland
> Sent: Wednesday, May 11, 2011 4:26 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Python Tools for Visual Studio now accepting contributions
>
>
>
> Jeff wrote:
>> This is excellent news.
>>
>> I think the plan should now be to deprecate the IronPython tools and
>> remove them from IronPython 3.0. They'll stay in future 2.7 releases,
>> but perhaps they should be disabled by default to make installing PTVS easier?
>
> That sounds like a good idea to me and it should be a pretty simple change.
>
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>



More information about the Ironpython-users mailing list