Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #94499 > unrolled thread

Re: what windows compiler for python 3.5?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: what windows compiler for python 3.5? Chris Angelico <rosuav@gmail.com> - 2015-07-24 21:04 +1000
    Re: what windows compiler for python 3.5? Brian Gladman <blindanagram@nowhere.net> - 2015-07-24 13:24 +0100
      Re: what windows compiler for python 3.5? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-25 01:33 +0100
    Re: what windows compiler for python 3.5? Brian Gladman <blindanagram@nowhere.net> - 2015-07-24 13:24 +0100
      Re: what windows compiler for python 3.5? ElChino <elchino@cnn.cn> - 2015-07-24 20:53 +0200
        Re: what windows compiler for python 3.5? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-07-24 19:51 -0400

#94499 — Re: what windows compiler for python 3.5?

On Fri, Jul 24, 2015 at 8:53 PM, Robin Becker <robin@reportlab.com> wrote:
> yes I build extensions for reportlab. Unfortunately, despite our MSDN
> subscription to the Visual Studio stuff we have no access to the Visual
> Studio Version 2015. Last one in my downloads is currently 2013. Pity.

Ah. You may well be somewhat out of luck for the moment, then; I've no
idea what status is during the betas. Once Python 3.5 is released, VS
2015 should also be available, or else the official compiler for
CPython 3.5 will probably be changed.

In the meantime, you could possibly ask on python-dev; Steve Dower of
Microsoft hangs out there, and he's the one who's driving the compiler
choice - he may be able to advise as to where to get the prerelease
compiler.

ChrisA

[toc] | [next] | [standalone]

#94502

On 24/07/2015 12:04, Chris Angelico wrote:
> On Fri, Jul 24, 2015 at 8:53 PM, Robin Becker <robin@reportlab.com> wrote:
>> yes I build extensions for reportlab. Unfortunately, despite our MSDN
>> subscription to the Visual Studio stuff we have no access to the Visual
>> Studio Version 2015. Last one in my downloads is currently 2013. Pity.
> 
> Ah. You may well be somewhat out of luck for the moment, then; I've no
> idea what status is during the betas. Once Python 3.5 is released, VS
> 2015 should also be available, or else the official compiler for
> CPython 3.5 will probably be changed.
> 
> In the meantime, you could possibly ask on python-dev; Steve Dower of
> Microsoft hangs out there, and he's the one who's driving the compiler
> choice - he may be able to advise as to where to get the prerelease
> compiler.

Visual Studio 2015 Community was relased earlier this week so there is
no need to work with the prerelease version.

[toc] | [prev] | [next] | [standalone]

#94539

On 24/07/2015 13:24, Brian Gladman wrote:
> On 24/07/2015 12:04, Chris Angelico wrote:
>> On Fri, Jul 24, 2015 at 8:53 PM, Robin Becker <robin@reportlab.com> wrote:
>>> yes I build extensions for reportlab. Unfortunately, despite our MSDN
>>> subscription to the Visual Studio stuff we have no access to the Visual
>>> Studio Version 2015. Last one in my downloads is currently 2013. Pity.
>>
>> Ah. You may well be somewhat out of luck for the moment, then; I've no
>> idea what status is during the betas. Once Python 3.5 is released, VS
>> 2015 should also be available, or else the official compiler for
>> CPython 3.5 will probably be changed.
>>
>> In the meantime, you could possibly ask on python-dev; Steve Dower of
>> Microsoft hangs out there, and he's the one who's driving the compiler
>> choice - he may be able to advise as to where to get the prerelease
>> compiler.
>
> Visual Studio 2015 Community was relased earlier this week so there is
> no need to work with the prerelease version.
>

No idea how I managed to miss that.  Still upgrade achieved and it only 
took around four hours 30 minutes.  We've terms like software, 
middleware, firmware, vapourware and so on and so forth, but I'm not 
certain what VS2015 comes under, explodedware possibly?

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [prev] | [next] | [standalone]

#94503

On 24/07/2015 12:04, Chris Angelico wrote:
> On Fri, Jul 24, 2015 at 8:53 PM, Robin Becker <robin@reportlab.com> wrote:
>> yes I build extensions for reportlab. Unfortunately, despite our MSDN
>> subscription to the Visual Studio stuff we have no access to the Visual
>> Studio Version 2015. Last one in my downloads is currently 2013. Pity.
> 
> Ah. You may well be somewhat out of luck for the moment, then; I've no
> idea what status is during the betas. Once Python 3.5 is released, VS
> 2015 should also be available, or else the official compiler for
> CPython 3.5 will probably be changed.
> 
> In the meantime, you could possibly ask on python-dev; Steve Dower of
> Microsoft hangs out there, and he's the one who's driving the compiler
> choice - he may be able to advise as to where to get the prerelease
> compiler.

Visual Studio 2015 Community was relased earlier this week so there is
no need to work with the prerelease version.

[toc] | [prev] | [next] | [standalone]

#94518

Brian Gladman wrote:

 > Visual Studio 2015 Community was relased earlier this week so there is
> no need to work with the prerelease version.

Hope MS have fixed all the "internal compiler errors".
E.g. trying to compile GeoIpApi-C [1], consistently reports:
   libGeoIP/regionName.c(7596): fatal error C1026: parser stack overflow,
   program too complex

here. The regionName.c look pretty lame, but not that complex IMHO.

[1] https://github.com/maxmind/geoip-api-c/blob/master/libGeoIP/regionName.c

[toc] | [prev] | [next] | [standalone]

#94538

On Fri, 24 Jul 2015 20:53:09 +0200, ElChino <elchino@cnn.cn> declaimed the
following:

>Brian Gladman wrote:
>
> > Visual Studio 2015 Community was relased earlier this week so there is
>> no need to work with the prerelease version.
>
>Hope MS have fixed all the "internal compiler errors".
>E.g. trying to compile GeoIpApi-C [1], consistently reports:
>   libGeoIP/regionName.c(7596): fatal error C1026: parser stack overflow,
>   program too complex
>
>here. The regionName.c look pretty lame, but not that complex IMHO.
>
>[1] https://github.com/maxmind/geoip-api-c/blob/master/libGeoIP/regionName.c
>

	My pessimist side is coming out:

Might be a deliberate restriction on the Community Edition (just like some
of the development environments for microcontrollers -- I have TIVA
"evaluation" boards with 256kB and 1MB flash but most of the free
development environments are locked at 32kB maximum code size; I'm still
not sure of TI's CCS 6, where CCS 5 explicitly gave full capability when it
recognized the built-in programming interface of the boards)
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web