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

Showing content from https://mail.python.org/pipermail/python-dev/2008-May/079848.html below:

[Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0

• Previous message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Next message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I'm beginning to wonder whether I'm the only one who cares about
> the Python 2.x branch not getting cluttered up with artifacts caused
> by a broken forward merge strategy.

I share your concern.  Seems to me that perhaps (not sure, but
perhaps) the rush to back-port from 3.x, and the concern about
minimizing pain of moving from 2.x to 3.x, has become the tail wagging
the dog.

Bill

• Previous message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Next message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• 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