A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-July/090434.html below:

[Python-Dev] Mercurial migration: progress report (PEP 385)

[Python-Dev] Mercurial migration: progress report (PEP 385) [Python-Dev] Mercurial migration: progress report (PEP 385)average dreamingforward at gmail.com
Sun Jul 5 21:36:20 CEST 2009
>> Is it really that confusing? I have never heard of anyone asking "what
>> is py3k?"
>
> Do you read python-list? It has been asked. Also, some people seem to
> think that py3k is different from python 3.

Personally, I vote for keeping the "3k" for 3000 (or is it 3072?).  I
believe that py3k represents a ideal that hasn't been reached, despite
being hoped for in python3.  By keeping it, it confers the idea
continual evolution *within* the language until that hypothetical
ideal is reached.  Clearly, there are times when a language reaches
only a local maximum, and must depart from itself to arrive at a more
global optimum (an annealing problem in the minimization of
frustration energy).  If py3k wasn't kept, another term would
eventually need to be invented.

marcos
More information about the Python-Dev mailing list

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