Re: [Python-Dev] Status of C compilers for Python on Windows

On 10/29/2014 11:37 AM, Steve Dower wrote: My ideal target (Utopia refined to be achievable) is for python-dev to handle the Python binaries themselves (already done) and to make them easy to bundle with applications/etc (I'm working on this for 3.5), and for PyPI to include pre-built wheels for

Re: [Python-Dev] Status of C compilers for Python on Windows

On 10/29/2014 4:05 PM, Paul Moore wrote: On 29 October 2014 15:31, Nathaniel Smith wrote: You can use Express editions of Visual Studio. IIUC, the express edition compilers are 32-bit only, and what you actually want are the "SDK compilers": https://github.com/cython/cython/wiki/64BitCythonEx

Re: [Python-Dev] Status of C compilers for Python on Windows

"For the paid versions, I'm going to assume that anyone who paid for a compiler and doesn't know where their copy is, probably can't be helped ;-)" You could link to visualstudio.com for the trial versions, and maybe to a page/post about the PSF's grants process if such a page exists. "And of co

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 23:49, Steve Dower wrote: > "For the paid versions, I'm going to assume that anyone who paid for a > compiler and doesn't know where their copy is, probably can't be > helped ;-)" > > You could link to visualstudio.com for the trial versions, and maybe to a > page/post about the

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 23:22, Nathaniel Smith wrote: >> Yeah, I know what you mean. My take on this is that I agree it's not >> easy if you don't know and can't get access to the information, but if >> you can, there's very little to it. > > That's great, but yeah. In case it helps as a data point, I

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, Oct 29, 2014 at 10:46 PM, Paul Moore wrote: > On 29 October 2014 22:19, Ethan Furman wrote: >>> Yeah, I wondered about that. I'll work up a patch for that. But the >>> more I think about it, it really is trivial: >> >> I am reminded of an interview question I was once asked which was pref

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 23:02, Ethan Furman wrote: > On 10/29/2014 03:46 PM, Paul Moore wrote: >> >> On 29 October 2014 22:19, Ethan Furman wrote: >>> >>> >>>- where one should be at when one starts the compile process >> >> >> I don't understand this. It's just "pip wheel foo" to build a wheel >>

Re: [Python-Dev] Status of C compilers for Python on Windows

> On Oct 29, 2014, at 7:02 PM, Ethan Furman wrote: > > On 10/29/2014 03:46 PM, Paul Moore wrote: >> On 29 October 2014 22:19, Ethan Furman wrote: >>> >>> - where one should be at when one starts the compile process >> >> I don't understand this. It's just "pip wheel foo" to build a wheel >>

Re: [Python-Dev] Status of C compilers for Python on Windows

On 10/29/2014 03:46 PM, Paul Moore wrote: On 29 October 2014 22:19, Ethan Furman wrote: - where one should be at when one starts the compile process I don't understand this. It's just "pip wheel foo" to build a wheel for foo (which will be downloaded), or "pip wheel ." or "python setup.p

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 22:19, Ethan Furman wrote: >> Yeah, I wondered about that. I'll work up a patch for that. But the >> more I think about it, it really is trivial: > > I am reminded of an interview question I was once asked which was prefaced > with: "Here's an easy one..." > > My reply was, if y

Re: [Python-Dev] Status of C compilers for Python on Windows

On 10/29/2014 03:09 PM, Paul Moore wrote: On 29 October 2014 20:26, Donald Stufft wrote: This sounds like something good for packaging.python.org Yeah, I wondered about that. I'll work up a patch for that. But the more I think about it, it really is trivial: I am reminded of an interview qu

Re: [Python-Dev] Status of C compilers for Python on Windows

> On Oct 29, 2014, at 6:09 PM, Paul Moore wrote: > > On 29 October 2014 20:26, Donald Stufft wrote: >> This sounds like something good for packaging.python.org > > Yeah, I wondered about that. I'll work up a patch for that. But the > more I think about it, it really is trivial: > > - For non-

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 20:26, Donald Stufft wrote: > This sounds like something good for packaging.python.org Yeah, I wondered about that. I'll work up a patch for that. But the more I think about it, it really is trivial: - For non-free MSVC, install the appropriate version, and everything just wor

Re: [Python-Dev] Status of C compilers for Python on Windows

This sounds like something good for packaging.python.org > On Oct 29, 2014, at 4:05 PM, Paul Moore wrote: > > On 29 October 2014 15:31, Nathaniel Smith wrote: >>> You can use Express editions of Visual Studio. >> >> IIUC, the express edition compilers are 32-bit only, and what you actually >>

Re: [Python-Dev] Status of C compilers for Python on Windows

Stephen J. Turnbull: the pain of using Windows is what drives me away from all of them. Enough that you are not able to make the software you write usable on Windows? I see your point and agree with it - I don't even like Windows much at all, but supporting it is important for plenty of reasons

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 October 2014 15:31, Nathaniel Smith wrote: >> You can use Express editions of Visual Studio. > > IIUC, the express edition compilers are 32-bit only, and what you actually > want are the "SDK compilers": > https://github.com/cython/cython/wiki/64BitCythonExtensionsOnWindows > > These are fre

Re: [Python-Dev] Impact of Windows PowerShell OneGet ?

> On Oct 29, 2014, at 3:34 PM, Glenn Linderman wrote: > > New package manager from M$... article here > . > > It seems doubtful that M$ will eliminate .msi (their obscure, hard to > configure and use, ins

[Python-Dev] Impact of Windows PowerShell OneGet ?

New package manager from M$... article here . It seems doubtful that M$ will eliminate .msi (their obscure, hard to configure and use, installation format), so it seems doubtful that the addition of OneGet

Re: [Python-Dev] Status of C compilers for Python on Windows

> On Oct 29, 2014, at 11:37 AM, Steve Dower wrote: > > Antoine Pitrou wrote: >> On Wed, 29 Oct 2014 11:07:53 -0400 >> Tres Seaver wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> On 10/29/2014 10:31 AM, R. David Murray wrote: >>> If you are writing code targeted for W

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, Oct 29, 2014 at 5:17 PM, David Cournapeau wrote: > > > On Wed, Oct 29, 2014 at 3:25 PM, Antoine Pitrou > wrote: > >> On Thu, 30 Oct 2014 01:09:45 +1000 >> Nick Coghlan wrote: >> > >> > Lots of folks are happy with POSIX emulation layers on Windows, as >> > they're OK with "basically wor

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, Oct 29, 2014 at 3:25 PM, Antoine Pitrou wrote: > On Thu, 30 Oct 2014 01:09:45 +1000 > Nick Coghlan wrote: > > > > Lots of folks are happy with POSIX emulation layers on Windows, as > > they're OK with "basically works" rather than "works like any other > > native application". "Basically

Re: [Python-Dev] Status of C compilers for Python on Windows

Antoine Pitrou wrote: > On Wed, 29 Oct 2014 11:07:53 -0400 > Tres Seaver wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 10/29/2014 10:31 AM, R. David Murray wrote: >> >> > If you are writing code targeted for Windows, I think you are very >> > likely to have an MSDN subscri

Re: [Python-Dev] Status of C compilers for Python on Windows

On Thu, 30 Oct 2014 01:09:45 +1000, Nick Coghlan wrote: > (Paul Moore already covered most of this, but I'll go into a bit more > detail in a couple of areas) > > On 29 October 2014 00:46, Tony Kelman wrote: > > Stephen J. Turnbull: > >> It should be evident by now that our belief is that the la

Re: [Python-Dev] Status of C compilers for Python on Windows

On 29 Oct 2014 14:47, "Antoine Pitrou" wrote: > > On Wed, 29 Oct 2014 10:31:50 -0400 > "R. David Murray" wrote: > > > On Wed, 29 Oct 2014 10:22:14 -0400, Tres Seaver wrote: > > > On 10/28/2014 11:59 PM, Stephen J. Turnbull wrote: > > > > > > > most developers on Windows do have access to Microso

Re: [Python-Dev] Status of C compilers for Python on Windows

On Thu, 30 Oct 2014 01:09:45 +1000 Nick Coghlan wrote: > > Lots of folks are happy with POSIX emulation layers on Windows, as > they're OK with "basically works" rather than "works like any other > native application". "Basically works" isn't sufficient for many > Python-on-Windows use cases thou

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, 29 Oct 2014 11:07:53 -0400 Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/29/2014 10:31 AM, R. David Murray wrote: > > > If you are writing code targeted for Windows, I think you are very > > likely to have an MSDN subscription of some sort if your packag

Re: [Python-Dev] Status of C compilers for Python on Windows

(Paul Moore already covered most of this, but I'll go into a bit more detail in a couple of areas) On 29 October 2014 00:46, Tony Kelman wrote: > Stephen J. Turnbull: >> It should be evident by now that our belief is that the large majority >> of Windows users is well-served by the current model

Re: [Python-Dev] Status of C compilers for Python on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2014 10:31 AM, R. David Murray wrote: > If you are writing code targeted for Windows, I think you are very > likely to have an MSDN subscription of some sort if your package > includes C code. I'm sure it's not 100%, though. My experience

Re: [Python-Dev] Status of C compilers for Python on Windows

On 30 October 2014 00:46, Antoine Pitrou wrote: > On Wed, 29 Oct 2014 10:31:50 -0400 > "R. David Murray" wrote: > >> On Wed, 29 Oct 2014 10:22:14 -0400, Tres Seaver >> wrote: >> > On 10/28/2014 11:59 PM, Stephen J. Turnbull wrote: >> > >> > > most developers on Windows do have access to Microso

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, 29 Oct 2014 10:31:50 -0400 "R. David Murray" wrote: > On Wed, 29 Oct 2014 10:22:14 -0400, Tres Seaver wrote: > > On 10/28/2014 11:59 PM, Stephen J. Turnbull wrote: > > > > > most developers on Windows do have access to Microsoft tool > > > > I assume you mean python-dev folks who work

Re: [Python-Dev] Status of C compilers for Python on Windows

On Wed, 29 Oct 2014 10:22:14 -0400, Tres Seaver wrote: > On 10/28/2014 11:59 PM, Stephen J. Turnbull wrote: > > > most developers on Windows do have access to Microsoft tool > > I assume you mean python-dev folks who work on Windows: it is certainly > not true for the vast majority of develoepr

Re: [Python-Dev] Status of C compilers for Python on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2014 11:59 PM, Stephen J. Turnbull wrote: > most developers on Windows do have access to Microsoft tool I assume you mean python-dev folks who work on Windows: it is certainly not true for the vast majority of develoeprs who use Python on W

Re: [Python-Dev] Status of C compilers for Python on Windows

"You might want to interact with Steve Dower off-list" FWIW, I'm happy to talk specifics off list, and have already been involved in a number of discussions with the numpy and Scipy guys wrt figuring out specific technical challenges or clarifying non obvious parts of dealing with Windows. (As

Re: [Python-Dev] PEP 475

On Wed, 29 Oct 2014 00:05:57 +0100 Victor Stinner wrote: > 2014-10-28 22:36 GMT+01:00 Antoine Pitrou : > > Is there an implementation somewhere? > > There is no implementation yet. This time, I chose to focus on the PEP > before working on an implementation :-) > > We can work on the implementat