Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-June/134918.html below:

[Python-Dev] Moving Python 3.5 on Windows to a new compiler

• 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 ]

Brett Cannon <bcannon at gmail.com> wrote:

> Nope. A new minor release of Python is a massive undertaking which is why
> we have saved ourselves the hassle of doing a Python 2.8 or not giving a
> clear signal as to when Python 2.x will end as a language.

Why not just define Python 2.8 as Python 2.7 except with a newer compiler?
I cannot see why that would be massive undertaking, if changing compiler
for 2.7 is neccesary anyway.

Sturla

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4