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/2010-June/100527.html below:

[Python-Dev] Future of 2.x.

[Python-Dev] Future of 2.x. [Python-Dev] Future of 2.x.Facundo Batista facundobatista at gmail.com
Wed Jun 9 14:55:43 CEST 2010
On Wed, Jun 9, 2010 at 8:58 AM, Paul Moore <p.f.moore at gmail.com> wrote:

> On that basis I'm +1 on Alexandre's proposal. A 3rd party planning on
> working on a 2.8 release (not that I think such a party currently
> exists) can step up and extract the relevant tickets for their later
> reference if they feel the need. Let's not stop moving forward for the
> convenience of a hypothetical 2.8 development team.

Yes, closing the tickets as "won't fix" and tagging them as
"will-never-happen-in-2.x" or something, is the best combination of
both worlds: it will clean the tracker and ease further developments,
and will allow anybody to pick up those tickets later.

(I'm +1 too to Alexandre's proposal, btw)

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
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