Re: Python Packaging Guide

2010-04-19 Thread Serafeim Zanikolas
On Fri, Apr 16, 2010 at 06:15:20PM +0530, Umang Varma wrote [edited]: > A few weeks back there was a small discussion I initiated on > #debian-python about a guide for new-comers to learn about packaging > Python applications and modules. I decided to update, restructure A big bravo for the effort

Is it worth back porting PEP 3147 to Python < 3.2?

2010-04-19 Thread Barry Warsaw
Apologies for the cross-post, but I want to make sure that everyone who cares about Python on both Debian and Ubuntu gets a chance to weigh in. On Friday, Guido approved and I landed the implementation of PEP 3147 on the py3k trunk (what will be Python 3.2). This allows multiple versions of Pytho

Skip Python 2.6 and use 2.7 as default in Squeeze?

2010-04-19 Thread Lino Mastrodomenico
Given how much work is required to change the default Python, does it make sense to just skip Python 2.6 and use 2.7 as the default Python version in Squeeze? The glaring downside of this is that 2.7 hasn't yet been released, but a feature-complete beta is available and, given how big the test sui

Re: Skip Python 2.6 and use 2.7 as default in Squeeze?

2010-04-19 Thread Cyril Brulebois
Hi Lino, Lino Mastrodomenico (20/04/2010): > Given how much work is required to change the default Python, does > it make sense to just skip Python 2.6 and use 2.7 as the default > Python version in Squeeze? Python 2.6 transition is already going on. > The glaring downside of this is that 2.7 h

Re: Skip Python 2.6 and use 2.7 as default in Squeeze?

2010-04-19 Thread Kumar Appaiah
On Tue, Apr 20, 2010 at 02:42:37AM +0200, Cyril Brulebois wrote: > > Python 2.7 is faster than 2.6 (in my limited tests from a few > > percents to more than 7 times faster, the latter with a small > > CPU-intensive math program), it has a few cool new toys, for many > > years in the future it will

Re: Is it worth back porting PEP 3147 to Python < 3.2?

2010-04-19 Thread Omer Zak
My take of the situation: Yes, please backport PEP 3147 to at least Python 2.7. The rationale: we'll need to support both Python 2.x and Python 3.x for several years, and it will be nice if the same library package can be made to support both 2.x and 3.x. It would also be nice to define a way to s

Re: Is it worth back porting PEP 3147 to Python < 3.2?

2010-04-19 Thread Julian Andres Klode
On Tue, Apr 20, 2010 at 06:50:26AM +0300, Omer Zak wrote: > My take of the situation: > Yes, please backport PEP 3147 to at least Python 2.7. > The rationale: we'll need to support both Python 2.x and Python 3.x for > several years, and it will be nice if the same library package can be > made to s