Date: Tue, 26 Jan 2010 08:56:11 -0500
From: Jason Tishler <jason@tishler.net>
To: cygwin@cygwin.com
Subject: Re: Python 2.6 ?
Message-id: <20100126135611.GA2212@tishler.net>
Mail-followup-to: cygwin@cygwin.com
References: <4B5EADFB.4010200@users.sourceforge.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
In-reply-to: <4B5EADFB.4010200@users.sourceforge.net>
User-Agent: Mutt/1.4.2.1i
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Yaakov,

On Tue, Jan 26, 2010 at 02:55:23AM -0600, Yaakov (Cygwin/X) wrote:
> What are your plans for upgrading the distro Python to 2.6?

I was waiting for Cygwin 1.7 to be released.  I guess I can't use that
excuse anymore... :,)

> I'm finally starting to see some programs require 2.6 now, so I think
> the time has finally come that to consider an upgrade.

Agreed, especially since the Python web site indicates the following:

    The current production versions are Python 2.6.4 and Python 3.1.1.

> Of course, any upgrade to Python affects a lot of packages,

Wow, I didn't realize there were so many Cygwin packages dependent on
Python:

    $ wget -q -O - http://mirror.nyi.net/cygwin/setup.ini | \
    grep '^requires:.* python' setup.ini | wc -l
    54

> so I hope that we can coordinate this in order to have a smooth
> transition.

What do you propose?  Should I release a Python 2.6 as experimental, use
alternatives, or another approach?

BTW, is the threading workaround mentioned in the following post still
necessary?

    http://cygwin.com/ml/cygwin/2009-07/msg00831.html

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple