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

Showing content from https://mail.python.org/pipermail/python-dev/2018-April/153200.html below:

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3

• Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Next message (by thread): [Python-Dev] Every Release Can Be a Mini "Python 4000", Within Reason (was (name := expression) doesn't fit the narrative of PEP 20)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow <ericsnowcurrently at gmail.com> wrote:
> In pondering our approach to future Python major releases, I found
> myself considering the experience we've had with Python 3.  The whole
> Py3k effort predates my involvement in the community so I missed a
> bunch of context about the motivations, decisions, and challenges.
> While I've pieced some of that together over the years now since I've
> been around, I've certainly seen much of the aftermath.  For me, at
> least, it would be helpful to have a bit more insight into the
> history. :)

Thanks, all, for the responses. :)

-eric

• Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Next message (by thread): [Python-Dev] Every Release Can Be a Mini "Python 4000", Within Reason (was (name := expression) doesn't fit the narrative of PEP 20)
• 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