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

Larry Hastings wrote: > CPython doesn't require OpenBLAS. Not that I am not receptive to the > needs of the numeric community... but, on the other hand, who in the > hell releases a library with Windows support that doesn't work with MSVC?! It uses AT&T assembly syntax instead of Intel assembly

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

Steve Dower wrote: > I don't have any official confirmation, but my guess would be that the > 64-bit compilers were omitted from the VC 2008 Express to save space > (bearing in mind that WinXP was the main target at that time, which had > poor 64-bit support, and very few people cared about build

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

On 10/10/2014 03:36 PM, Tres Seaver wrote: On 10/10/2014 05:26 AM, Larry Hastings wrote: IMO the benefit from supporting other compilers on Windows is negligible Did you miss the OP's point that OpenBLAS cannot be compiled with MSVC, raising the priority of mingw-buildable extensions for numer

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

> On Oct 10, 2014, at 6:59 PM, Steve Dower wrote: > > Cross compilation is a valid issue, but I hope that build services like > Appveyor also help out here. There is regular talk about the PSF/PyPI > providing something similar, though I have doubts about its feasibility under > any model oth

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

>From Victor Stinner: > I know that it's hard to replace Visual Studio. I don't want to do it right > now, but I would like to discuss that with you. I have read the rest of the thread, but I want to start from this point. I'm probably going to run off in random directions since there are a lot

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

On 10 October 2014 17:28, Mark Lawrence wrote: > There are 55 open issues on the bug tracker with mingw in the title. It's not easy to tell, but on a spot check a fair proportion of them seem to be about distutils/extension builds. And a lot of the rest are related to http://bugs.python.org/issue

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

On 10.10.2014 14:05, Paul Moore wrote: > On 10 October 2014 10:50, Victor Stinner wrote: >> Is MinGW fully compatible with MSVS ABI? I read that it reuses the >> MSVCRT, but I don't know if it's enough. I guess that a full ABI >> compatibility means more than just using the C library, calling >> c

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

On 10/10/2014 01:29, Victor Stinner wrote: === MinGW Some people tried to compile Python. See for example: https://bitbucket.org/puqing/python-mingw We even got some patches: http://bugs.python.org/issue3871 (rejected) There are 55 open issues on the bug tracker with mingw in the title. S

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Fri, 10 Oct 2014 12:08:54 -0400 "R. David Murray" wrote: > On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > > On 10/10/14 17:56, Chris Angelico wrote: > > > Could I write a little > > > monitor at my end that asks every hour if my buildbots can be seen? > > > > AFAIK maintainers already

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > On 10/10/14 17:56, Chris Angelico wrote: > > Could I write a little > > monitor at my end that asks every hour if my buildbots can be seen? > > AFAIK maintainers already get an email if the buildbot vanishes long > enough. I am more intereste

Re: [Python-Dev] Sad status of Python 3.x buildbots

It's https://bugs.python.org/issue19884 On Fri, Oct 10, 2014, at 12:08, R. David Murray wrote: > On Fri, 10 Oct 2014 18:00:06 +0200, Jesus Cea wrote: > > On 10/10/14 17:56, Chris Angelico wrote: > > > Could I write a little > > > monitor at my end that asks every hour if my buildbots can be seen?

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2014-10-03 - 2014-10-10) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open4598 (-33) closed 29769 (+90) total 34367 (+57) Open issues wit

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 10/10/14 17:45, Jesus Cea wrote: > Thanks for your patience and for notifying me issues when you suffer them. Another issue is changes that actually breaks buildbots and I don't actually know where to start debugging. For instance, currently:

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 10/10/14 17:56, Chris Angelico wrote: > Could I write a little > monitor at my end that asks every hour if my buildbots can be seen? AFAIK maintainers already get an email if the buildbot vanishes long enough. I am more interested in getting an email when my buildbot is consistently red because

Re: [Python-Dev] mUTF-7 support?

Jesus Cea wrote: > On 10/10/14 02:43, Victor Stinner wrote: > >>> What is the current behaviour of imaplib in Python 3.4 with non-ASCII > >>> characters in mailbox names? > >> > >> It breaks. Crash & burn. > > > > Oh ok. So in short, imaplib doesn't work on Python 3: > > Actually, it doesn't wor

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Sat, Oct 11, 2014 at 2:45 AM, Jesus Cea wrote: > On 03/09/14 02:37, Antoine Pitrou wrote: > >> I'm not sure that's an answer to the problem. What we need is not more >> machines, but dedicated buildbot maintainers. > > I would love to get an email if my buildbots are consistently RED for a > fe

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03/09/14 02:37, Antoine Pitrou wrote: > I'm not sure that's an answer to the problem. What we need is not more > machines, but dedicated buildbot maintainers. I would love to get an email if my buildbots are consistently RED for a few hours. In the past Antoine, Victor and others pinged me ab

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

On 10 October 2014 15:36, Tres Seaver wrote: > On 10/10/2014 05:26 AM, Larry Hastings wrote: >> IMO the benefit from supporting other compilers on Windows is >> negligible > > Did you miss the OP's point that OpenBLAS cannot be compiled with MSVC, > raising the priority of mingw-buildable extensio

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

I don't think this is exactly on the same axis. Being able Python to build with a free compiler won't change this issue. Scientific Python won't be only the free compiler version, Visual Studio would remain the main citizen. It may fragment a little bit more the environment with people needing to p

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/10/2014 05:26 AM, Larry Hastings wrote: > IMO the benefit from supporting other compilers on Windows is > negligible Did you miss the OP's point that OpenBLAS cannot be compiled with MSVC, raising the priority of mingw-buildable extensions for

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

On Thu, Oct 9, 2014 at 7:29 PM, Victor Stinner wrote: > Hi, > > Windows is not the primary target of Python developers, probably > because most of them work on Linux. Official Python binaries are > currently built by Microsoft Visual Studio. Even if Python developers > get free licenses thanks for

Re: [Python-Dev] Internationalized email support (was mUTF-7 support?)

On Fri, 10 Oct 2014 16:16:24 +0900, "Stephen J. Turnbull" wrote: > R. David Murray writes: > > > in the email address (and can't contain non-ASCII yet...we need RFC 6855 > > support for that, and I'm not sure *anybody* has that yet). > > If it's an RFC, *somebody* has it *somewhere*. :-) Ah,

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

On 10 October 2014 10:50, Victor Stinner wrote: > Is MinGW fully compatible with MSVS ABI? I read that it reuses the > MSVCRT, but I don't know if it's enough. I guess that a full ABI > compatibility means more than just using the C library, calling > convention and much more. MinGW can be made t

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

Victor Stinner gmail.com> writes: > > Hi, > > Windows is not the primary target of Python developers, probably > because most of them work on Linux. Official Python binaries are > currently built by Microsoft Visual Studio. Even if Python developers > get free licenses thanks for Microsoft, I w

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

Merlijn van Deen wrote: > VC++ 2008/2010 EE do not *bundle* a 64-bit compiler, Actually it does, but it is not available from the UI. You can use it from the command line, though. Sturla ___ Python-Dev mailing list Python-Dev@python.org https://mail

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

Larry Hastings wrote: > So as a practical matter I think I'd prefer if we continued to only > support MSVC. In fact I'd prefer it if we removed support for other > Windows compilers, instead asking those maintainers to publish their own > patches / repos, in the way that Stackless does. The sci

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

Victor Stinner wrote: > Is MinGW fully compatible with MSVS ABI? I read that it reuses the > MSVCRT, but I don't know if it's enough. Not out of the box. See: https://github.com/numpy/numpy/wiki/Mingw-static-toolchain Sturla ___ Python-Dev mailin

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

Larry Hastings wrote: > Just to make something clear that may not be clear to non-Windows > developers: the C library is implicitly part of the ABI. MacOS X also has this issue, but it less known amon Mac developers! There tends to be multiple versions of the C library, one for each SDK versio

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

On 10 October 2014 02:29, Victor Stinner wrote: > The free version (Visual Studio Express) only supports 32-bit > VC++ 2008/2010 EE do not *bundle* a 64-bit compiler, but it's certainly possible to build 64-bit applications by using the compiler in the (also free) Windows SDK: http://jenshuebel

Re: [Python-Dev] mUTF-7 support?

I think the consensus so far is that this is a good idea. I just opened . Thanks for your feedback. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea

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

On 10.10.2014 11:26, Larry Hastings wrote: > > On 10/10/2014 08:07 AM, Paul Moore wrote: >> On 10 October 2014 01:29, Victor Stinner wrote: >>> What about the Python stable ABI? Would it be broken if we use a >>> different compiler? >>> >>> What about third party Python extensions? >>> >>> What a

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

Hi, Paul Moore wrote: > The key point for me is that any supported build on Windows supports > the exact same ABI. It looks like ABI compatibility is a goal of Clang on Windows: http://clang.llvm.org/docs/MSVCCompatibility.html http://blog.llvm.org/2014/07/clangllvm-on-windows-update.html

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

2014-10-10 11:18 GMT+02:00 Sturla Molden : > If you build Python yourself, you can (more or less) use whichever version > of Visual Studio you want. There is nothing that prevents you from building > Python 2.7 or 3.4 with MSVC 14. Python 2.7 provides project files (PCbuild/*) for Visual Studio 20

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

On 10/10/2014 08:07 AM, Paul Moore wrote: On 10 October 2014 01:29, Victor Stinner wrote: What about the Python stable ABI? Would it be broken if we use a different compiler? What about third party Python extensions? What about external dependencies like gzip, bz2, Tk, Tcl, OpenSSL, etc.? T

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

Paul Moore wrote: > Having said that, I'm personally not interested in this, as I am happy > with MSVC Express. Python 3.5 will be using MSVC 14, where the express > edition supports both 32 and 64 bit. If you build Python yourself, you can (more or less) use whichever version of Visual Studio y

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

Nathaniel Smith wrote: > You may want to get in touch with Carl Kleffner -- he's done a bunch > of work lately on getting a mingw-based toolchain to the point where > it can build numpy and scipy. To build *Python extensions*, one can use Carl's toolchain or the VC9 compiler for Python 2.7 that

Re: [Python-Dev] mUTF-7 support?

On 10/10/14 04:41, R. David Murray wrote: > Specifically, it is about what we might better term mailbox > *folders*...that is, not what you would normally think of as the > 'mailbox name', which is usually understood to be the thing before the @ > in the email address (and can't contain non-ASCII y

Re: [Python-Dev] mUTF-7 support?

R. David Murray writes: > in the email address (and can't contain non-ASCII yet...we need RFC 6855 > support for that, and I'm not sure *anybody* has that yet). If it's an RFC, *somebody* has it *somewhere*. :-) ___ Python-Dev mailing list Python-Dev

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

On 10 October 2014 01:29, Victor Stinner wrote: > What about the Python stable ABI? Would it be broken if we use a > different compiler? > > What about third party Python extensions? > > What about external dependencies like gzip, bz2, Tk, Tcl, OpenSSL, etc.? The key point for me is that any supp