[Python-Dev] PEP 0404 and VS 2010

MRAB python at mrabarnett.plus.com
Thu Nov 21 03:35:17 CET 2013

On 20/11/2013 23:36, Christian Tismer wrote:
> Hey Barry,
> On 20.11.13 23:30, Barry Warsaw wrote:
>> On Nov 20, 2013, at 09:52 PM, Christian Tismer wrote:
>>> Many customers are forced to stick with Python 2.X because of other products,
>>> but they require a Python 2.X version which can be compiled using Visual
>>> Studio 2010 or better.  This is considered an improvement and not a bug fix,
>>> where I disagree.
>> I'm not so sure about that.  Python 2.7 can still get patches to help extend
>> its useful life by allowing it to be built with newer compiler suites.  I
>> believe this has already been done for various Linux compilers.  I see no
>> non-technical reason why Python 2.7 can't be taught how to build with VS 2010
>> or newer.  Details are subject to RM approval, IMHO.
>>> I have created a very clean Python 2.7.6+ based CPython with the Stackless
>>> additions, that compiles with VS 2010, using the adapted project structure
>>> of Python 3.3.X, and I want to publish that on the Stackless website as the
>>> official "Stackless Python 2.8". If you consider Stackless as official ;-) .
>>> This compiler change is currently the only deviation from CPython 2.7,
>>> but we may support a few easy back-ports on customer demand. We don'd add
>>> any random stuff, of course.
>> I think you're just going to confuse everyone if you call it "Stackless Python
>> 2.8" and it will do more harm than good.
> Barry, that's a good thing! This way I have a chance to get my build in
> at all.
> And that's the question, after re-thinking:
> Where can I check my change in, if it is going to be accepted as a valid
> 2.7 bug fix (concerning VS 2008 as a bug, that is is)?
> I was intending to do this since a year but was stopped by MVL's influence.
> Maybe this needs to be re-thought, since I think different.
> What I do not know:
> Should I simply check this in to a python 2.7.x-VS2010 branch?
> Or what do you suggest, then?
> In any case, my question still stands, and I will do something with the
> Stackless branch by end of November. Please influence me ASAP, I don't
> intend to do any harm, but that problem is caused simply by my existence,
> and I want to stick with that for another few decades.
> If I think something must be done, then I have my way to do it.
> If you have good reasons to prevent this, then you should speak up in the
> next 10 days, or it will happen. Is that ok with you?
> Hugs -- your friend Chris
You could call it "Spython" instead!

More information about the Python-Dev mailing list