On 5/11/2011 3:39 PM, Dino Viehland wrote:
Keith 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 "
Jeff wrote:
> 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 Te
Keith 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
com
> www.wintellect.com
>
> -Original Message-
> From: users-boun...@lists.ironpython.com
> [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland
> Sent: Wednesday, May 11, 2011 4:26 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Python To
n.com
[mailto:users-boun...@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
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
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?
- Jeff
On Wed, May 11, 2011 at 1:13 PM, Dino Viehland
We've been in a difficult place with having two sets of tools for Visual Studio
that both work with IronPython. Those are the existing IronPython Tools that
shipped w/ 2.7 and the newer Python Tools for Visual Studio which are derived
from the original IronPython code base. To make things more