Prev: CFP for Surge Scalability Conference 2010
Next: IMAP Problems
From: Terry Reedy on 5 Jul 2010 01:44
On 7/4/2010 7:58 PM, John Nagle wrote:

> The "incompatible with all extension modules I need" part
> is the problem right now. A good first step would be to
> identify the top 5 or 10 modules that are blocking a move to
> Python 3 by major projects with many users.

Let me repeat. Last September, if not before, Guido identified numpy as
a top package blocking moves by other packages and projects. I am not
sure what he thought, but I consider it number 1. He encouraged the
numpy people to produce a 3.x version even though some did not see any
personal benefit. We supposedly will see numpy for 3.2. If we actually
do, other dominoes will fall into place.

I you have any other ideas about other top blockers, please share them.

--
Terry Jan Reedy

From: John Nagle on 5 Jul 2010 02:56
On 7/4/2010 10:44 PM, Terry Reedy wrote:
> On 7/4/2010 7:58 PM, John Nagle wrote:
>
>> The "incompatible with all extension modules I need" part
>> is the problem right now. A good first step would be to
>> identify the top 5 or 10 modules that are blocking a move to
>> Python 3 by major projects with many users.
>
> Let me repeat. Last September, if not before, Guido identified numpy as
> a top package blocking moves by other packages and projects. I am not
> sure what he thought, but I consider it number 1. He encouraged the
> numpy people to produce a 3.x version even though some did not see any
> personal benefit. We supposedly will see numpy for 3.2. If we actually
> do, other dominoes will fall into place.
>
> I you have any other ideas about other top blockers, please share them.

The Twisted team has a list of what they need:

"http://stackoverflow.com/questions/172306/how-are-you-planning-on-handling-the-migration-to-python-3"

* Zope Interface
* PyCrypto
* PyOpenSSL
* PyGTK


John Nagle

From: Terry Reedy on 5 Jul 2010 14:42
On 7/5/2010 2:56 AM, John Nagle wrote:
> On 7/4/2010 10:44 PM, Terry Reedy wrote:

>> I you have any other ideas about other top blockers, please share them.
>
> The Twisted team has a list of what they need:
>
> "http://stackoverflow.com/questions/172306/how-are-you-planning-on-handling-the-migration-to-python-3"
>
>
> * Zope Interface
> * PyCrypto
> * PyOpenSSL
> * PyGTK

Good start. Now what is blocking those four?
Lack of developer interest/time/ability?
or something else that they need?

--
Terry Jan Reedy

From: Terry Reedy on 5 Jul 2010 14:49
On 7/5/2010 6:04 AM, David Cournapeau wrote:
> On Mon, Jul 5, 2010 at 12:44 PM, Terry Reedy<tjreedy(a)udel.edu> wrote:
[snip]

> I think numpy will work for 3.1 as well

If numpy were released today for 3.1 (or even anytime before 3.2), that
would be great. It would let those waiting for it that it is real and
that they can go ahead on their ports.

Part of the reason for the 3.2 core-change moratorium was to let
3rd-party packages target 3.2 by working with 3.1. If they finish and
release sooner (as some have), even better. Unless they depend on
something that changes in the stdlib, porting for one should pretty much
be porting for both.

> (I don't know about 3.0, but
> my understanding is that there is no point into even looking at that
> release).

Agreed.


--
Terry Jan Reedy

From: John Nagle on 5 Jul 2010 18:28
On 7/5/2010 12:35 PM, Kevin Walzer wrote:
> On 7/5/10 2:56 AM, John Nagle wrote:
>
>> * PyCrypto
>> * PyOpenSSL
>
> These, and Mark Pilgrim's feedparser, need to be 3.x compatible before I
> can think about Python 3.x.

There's been an attempt to port "feedparser" to 3.0, but
that needed a port of BeautifulSoup:

http://code.google.com/p/feedparser/issues/detail?id=215

They also had some problems with "chardet".

John Nagle

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: CFP for Surge Scalability Conference 2010
Next: IMAP Problems