Guido van Rossum warns agains breaking api while porting to python 3.0:
http://www.artima.com/weblogs/viewpost.jsp?thread=227041
2007/8/29 Behdad Esfahbod <[EMAIL PROTECTED]>:
> On Wed, 2007-08-29 at 13:52 -0400, Behdad Esfahbod wrote:
>>
>> - Do things more Pythonesque. Looking at Pango bindin
We definitely need such a tool. But I think it will be very tricky.
> Some programs are using subclasses of subclasses of subclasses with a
> bunch of overridden methods. That could be a little bit hard to
> analyze... What about some kind of compatibility layer? Just a
> thought...
Hi
I defini
Fernando San Martín Woerner wrote:
El mié, 29-08-2007 a las 23:36 +0200, Andi Albrecht escribió:
2007/8/29, Johan Dahlin <[EMAIL PROTECTED]>:
Hi Johan and all,
in general I think it is a very good idea to port PyGTK to Python 3.x
as soon as possible. The api must not be stable with the fist
El mié, 29-08-2007 a las 23:36 +0200, Andi Albrecht escribió:
> 2007/8/29, Johan Dahlin <[EMAIL PROTECTED]>:
>
> Hi Johan and all,
>
> in general I think it is a very good idea to port PyGTK to Python 3.x
> as soon as possible. The api must not be stable with the fist alpha
> release, but it need
2007/8/29, Johan Dahlin <[EMAIL PROTECTED]>:
Hi Johan and all,
in general I think it is a very good idea to port PyGTK to Python 3.x
as soon as possible. The api must not be stable with the fist alpha
release, but it need to be stable at least with one of the first
betas. We'll have to port a bun
Johan Dahlin a écrit :
It is different from the old 2.x series in the sense that it will not
be backwards compatible with the old python releases. A program
written for Python 2.x will not run under Python 3.x unless it
restricts itself to a tiny tiny subset which is really not practical
(fo
John Ehresman wrote:
Just keep in mind that a production ready python 3.0 is a long time
away. You're right to be thinking about it because people who like to
play with things will try to do things with it. You might want to delay
declaring any api stable until after python 3.0 final is out t
Just keep in mind that a production ready python 3.0 is a long time
away. You're right to be thinking about it because people who like to
play with things will try to do things with it. You might want to delay
declaring any api stable until after python 3.0 final is out to allow
time for thin
Greetings
I'd like to ask for input on how the Python 3.0 transition is going to
affect GNOME.
Python 3.0 is the current development focus of the Python community.
It is different from the old 2.x series in the sense that it will not be
backwards compatible with the old python releases. A pro
