[IronPython] Python Tools for Visual Studio

Dino Viehland dinov at microsoft.com
Thu Mar 10 06:39:23 PST 2011

Can you elaborate on "efficient"?  Do you mean response time or actual usefulness?  

IronPython does take a little while to bring up members for a type you haven't 
completed against yet because reflection is slow.  But for CPython we have a separate
database that's much faster.

If it's actual usefulness you may find the PyTools analysis to be better as there have
been some general improvements and bug fixes there.  If you have some specific
repros I'd love to hear about them so we can fix them.

> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-
> bounces at lists.ironpython.com] On Behalf Of Federico Vaggi
> Sent: Thursday, March 10, 2011 6:37 AM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Python Tools for Visual Studio
> Thanks a lot for all the work Dino, I will give it a try for sure.
> I am not sure what other IDE people use for Python code writing, but I found
> that the auto-complete feature in pydev (the Eclipse plug-in) was a lot more
> efficient than the autocomplete for Ironpython.
> Federico
> On 10/03/2011 15:30, Dino Viehland wrote:
> > (I'll post this on my blog as soon as I can login into it, but it's been so long
> I'm having issues.  Anyway it seems appropriate for this alias as well):
> >
> > Some people may have been wondering what I've been working on since
> IronPython was released into the wild and late last night we announced it -
> Python Tools for Visual Studio [http://pytools.codeplex.com/].  For me this
> was an awesome opportunity to continue work on a Python focused open
> source project at Microsoft. I'm particularly excited I can extend the work we
> did to support IronPython in Visual Studio and add in support for CPython
> and other Python implementations.  I'm also really happy to be able to
> continue work with the Python community.
> >
> > PTVS keeps all the features we had in IronPython Tools for VS and adds a
> bunch of new features.  For starters we add support for both REPLs and
> debugging in CPython and other Python implementations.  We also add
> profiling support for CPython, support for multiple language versions (2.5
> through 3.2), and attach to process for CPython processes - both local and
> remote.  Meanwhile we still support all the features we had before including
> great intellisense and drag and drop GUI development for IronPython.
> >
> > But we're also focusing on developing new features in a specific area - High
> Performance Computing.  For our first beta we've focused on enabling two
> different scenarios - batch computing via MPI and interactive computing via
> IPython.  For batch computing we support publishing to and running on the
> cluster via a simple "F5" scenario .  If you're not yet ready to run on the
> cluster you can do the same multi-process launch on the local machine.  For
> interactive development we are focusing on the bleeding edge of IPython
> (.11+) where the new architecture is designed from the ground up to
> support parallel computing and alternate REPL UIs.
> >
> > If you're an IronPython user I encourage you to give the new tools a try -
> you'll first need to uninstall the tools feature in IronPython 2.7RC2 which you
> can do simply by re-running the MSI and choosing the change option.  If
> you're a CPython user I hope you'll also give it a try - you should find that it'll
> support your existing CPython installs for Python 2.5 through 3.2.  Thanks - I
> look forward to hearing your feedback.
> >
> > _______________________________________________
> > 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 Users mailing list