python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]

2010-04-20 Thread Rick Thomas
On Apr 20, 2010, at 2:30 AM, Jimmy Johnson wrote: If I was you I would start by finding out why python-twisted-core is not getting upgraded to the latest version that's in the repos and so on, with a little investigating I'm sure you will find what has broken your system, it may help to us

Re: python 2.6 deb for lenny ?

2010-04-20 Thread Fabio Tranchitella
* 2010-04-21 01:17, Bernd Zeimetz wrote: > I think Fabio (kob...@d.o) also wanted to / is working on a backport, > might make sense to co-maintain that with him. CCed him :) I'm definitely interested in co-maintaining the backport (and using my own backport in production already). I'll have a look

Re: Python Packaging Guide

2010-04-20 Thread Umang Varma
On 21/04/10 05:01, Jakub Wilk wrote: Who is your target audience? If you want this document to be read by packaging newbies, then this document is terribly incomplete. That, I believe, would be because of my very limited knowledge in the field. Although I may not have explicitly said this initia

Re: Python Packaging Guide

2010-04-20 Thread Jakub Wilk
* Umang Varma , 2010-04-18, 08:30: My general impression is that it's yet another (very) bad piece of documentation. Feel free to ignore my opinion however, as I'm already prejudiced. :P It's hard to ignore your opinion (or for that matter, that of any DD here). When you say very bad, it is cle

Re: python 2.6 deb for lenny ?

2010-04-20 Thread Bernd Zeimetz
On 04/01/2010 10:27 AM, Toni Mueller wrote: > I'm sorry to say that I forgot to upload my semi-broken attempts - just > "fixed" it - maybe they still provide a useful starting point: > >> http://people.debian.org/~toni/python2.6/ > > > Please send feedback my way! I think Fabio (kob...@d.o) al

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

2010-04-20 Thread Piotr Ożarowski
[Barry Warsaw, 2010-04-20] > If 10.10 includes > only Python 2.7, then sure, we'll only back port to that version. why do you want to backport it to 2.X for a single python2.x package? -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc

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

2010-04-20 Thread Piotr Ożarowski
[Barry Warsaw, 2010-04-20] > On Apr 20, 2010, at 10:14 AM, Piotr Ożarowski wrote: > > >[Omer Zak, 2010-04-20] > >> 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, a

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

2010-04-20 Thread Scott Kitterman
On Monday, April 19, 2010 05:53:05 pm Barry Warsaw wrote: > 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 trun

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

2010-04-20 Thread Omer Zak
On Tue, 2010-04-20 at 15:39 -0400, Barry Warsaw wrote: > On Apr 20, 2010, at 06:50 AM, 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

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

2010-04-20 Thread Barry Warsaw
On Apr 20, 2010, at 10:14 AM, Piotr Ożarowski wrote: >[Omer Zak, 2010-04-20] >> 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 pa

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

2010-04-20 Thread Barry Warsaw
On Apr 20, 2010, at 06:50 AM, 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 support both 2.x

Re: ITP: nltk -- A suite of Python libraries for natural language processing

2010-04-20 Thread Jakub Wilk
* C.J. Adams-Collier , 2010-04-20, 09:02: It is already being worked on. The package is being hosted on alioth and seems to build for me. I don't know what is keeping it from being rfs'd. Maybe robin knows? are you talking about Robin Munn? I'm not sure if he can sponsor (is he DD?). I can

Re: ITP: nltk -- A suite of Python libraries for natural language processing

2010-04-20 Thread C.J. Adams-Collier
On Tue, 2010-04-20 at 10:48 -0300, Luciano Bello wrote: > El Jue 08 Abr 2010, Luciano Bello escribió: > > El Mié 07 Abr 2010, C.J. Adams-Collier escribió: > > > It is already being worked on. The package is being hosted on alioth and > > > seems to build for me. I don't know what is keeping it fr

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

2010-04-20 Thread Piotr Ożarowski
[Omer Zak, 2010-04-20] > 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. you canno

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

2010-04-20 Thread Eike Nicklas
On Mon, 19 Apr 2010 19:46:48 -0500 Kumar Appaiah wrote: > But it would be nice to see Python 2.7 in Debian soon. :-) > It's available in experimental (not the latest beta, though). But indeed it would be great to have the 2.6->2.7 transition started a little earlier than the 2.5->2.6 one :-) p