<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">We&#8217;ve been in a difficult place with having two sets of tools for Visual Studio that both work with IronPython.&nbsp; 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.&nbsp; To make things more difficult we&#8217;ve been living in a world where you could contribute back to IronPython Tools but contributions weren&#8217;t being accepted back to PTVS.&nbsp; That&#8217;s obviously not the best environment for encouraging
 users to submit changes back and today I&#8217;m happy to announce that we&#8217;ve fixed this problem and we&#8217;re now accepting contributions back to PTVS!&nbsp;
<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">If you&#8217;re interested in contributing back feel free to fork PTVS (<a href="http://pytools.codeplex.com/SourceControl/network">http://pytools.codeplex.com/SourceControl/network</a>) and submit a pull request for your changes.&nbsp; Basic contribution
 guidelines are available here: <a href="http://pytools.codeplex.com/wikipage?title=Contributing%20to%20PTVS&amp;version=1">
http://pytools.codeplex.com/wikipage?title=Contributing%20to%20PTVS&amp;version=1</a> and instructions for getting setup to build are available here:
<a href="http://pytools.codeplex.com/wikipage?title=Build%20Instructions%20for%20PTVS">
http://pytools.codeplex.com/wikipage?title=Build%20Instructions%20for%20PTVS</a><o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>