Marco Peereboom wrote:
I am talking about custom apps that you don't see. There is a lot of
python code out there running on 2.5. I am not making it up; I know of
several shops that do everything in 2.5.
I am all for making 2.6 the default but eliminating 2.5 from the tree
seems like a bad move to me. Now you'll force people to maintain their
own port even though there is no real benefit for us to remove it.
Anyway, just my $0.02 and feel free to ignore me.
On Wed, Jun 16, 2010 at 05:37:01PM +0100, Federico G. Schwindt wrote:
On Wed, Jun 16, 2010 at 11:26:43AM -0500, Marco Peereboom wrote:
I would leave 2.5 alone too. I am sure there are apps that require it
and it really doesn't hurt anything in the tree.
Unfortunate side effect of these types of "languages".
if there is any app that needs 2.5, we can fix it to work with 2.6.
i don't want to leave it just in case. the just in case wastes more time
than it currently helps.
if we leave 2.5 around but we make 2.6 the default, we'll need to check
with 2.5 still and people might avoid fixing it just because 2.5 is there.
if you have any specific app i'm mind i'm happy to take a look and fix it
but since no apps in the tree seems to depends on 2.5 (last one was py-dpkt
that was updated recently) moving to 2.6 makes sense.
f.-
Python 2.7 will be released this year (July?).
That will be the last of 2.x series.
Either jump to 3.x or wait for 2.7, please...
-pekka-