[Python-Dev] Moving Python 3.5 on Windows to a new compiler (original) (raw)
Eli Bendersky eliben at gmail.com
Sat Jun 7 01:45:06 CEST 2014
- Previous message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Next message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jun 6, 2014 at 4:32 PM, Sturla Molden <sturla.molden at gmail.com> wrote:
Brian Curtin <brian at python.org> wrote:
> Well we're certainly not going to assume such a thing. I know people do > that, but many don't (I never have). If Python 2.7 users are left with a dead compiler on Windows, they will find a solution. For example, Enthought is already bundling their Python distribution with gcc 2.8.1 on Windows.
While we're at it, Clang in nearing a stage where it can compile C and C++ on Windows with ABI-compatibility to MSVC (yes, even C++) -- see http://clang.llvm.org/docs/MSVCCompatibility.html for more details. Could this help?
Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140606/72ba9152/attachment.html>
- Previous message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Next message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]