<div dir="ltr">On Wed, Nov 20, 2013 at 12:52 PM, Christian Tismer <span dir="ltr"><<a href="mailto:tismer@stackless.com" target="_blank">tismer@stackless.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">according to pep 404, there will never be an official Python 2.8.<br>
The migration path is from 2.7 to 3.x.<br>
<br>
I agree with this strategy in almost all consequences but this one:<br>
<br>
Many customers are forced to stick with Python 2.X because of other<br>
products, but they require a Python 2.X version which can be compiled<br>
using Visual Studio 2010 or better.<br>
This is considered an improvement and not a bug fix, where I disagree.<br></blockquote><div><br></div><div style>maybe we need to continue that discussion then -- and call this a bug fix.</div><div style><br></div><div style>
It seems clear to me that the Python X.Y version number specifies a set of features and their implementation, not a particular build with a particular compiler. So a python 2.7 build with VS2010 (or any other compiler for that matter) is still python 2.7.</div>
<div style><br></div><div style>And for what it's worth, stackless aside I'd love to see a python2.7 binary built with a newer MS compiler -- for instance, the latest pyton plugin for Visual Studio lets you debug python and C extensions side by side -- very cool, and only available with VS2012.</div>
<div style><br></div><div style>Sorry I'm out of the loop, but are there patched required to use newer VS compilers to build 2.7? or is this really just a matter of what the official python org builds are build with?</div>
<div style><br></div><div style>-Chris</div><div style><br></div></div>-- <br><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>
Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a>
</div></div>