Re: [pygtk] CVS branches and plans for the future.

2003-09-07 Thread Andrew P. Lentvorski, Jr.
On Sun, 7 Sep 2003, John K Luebs wrote: Currently, pygtk seems to be supporting both Python 2.2 and 2.3. What does 2.3 have that 2.2 does not have that would warrant ditching support for 2.2? Lots of Unicode fixes and some object system cleanups. To be clear, I am *not* advocating that pygtk

Re: [pygtk] CVS branches and plans for the future.

2003-09-07 Thread James Henstridge
On 07/09/03 14:27, John K Luebs wrote: Currently, pygtk seems to be supporting both Python 2.2 and 2.3. What does 2.3 have that 2.2 does not have that would warrant ditching support for 2.2? If it ain't broke... Well, there is one feature found in Python 2.3's C API that could be useful, and

Re: [pygtk] CVS branches and plans for the future.

2003-09-07 Thread Tim Evans
John K Luebs wrote: Currently, pygtk seems to be supporting both Python 2.2 and 2.3. What does 2.3 have that 2.2 does not have that would warrant ditching support for 2.2? One small feature that might be nice is that Python 2.3 makes it easy for types created by C code to have class methods, by

Re: [pygtk] CVS branches and plans for the future.

2003-09-06 Thread Andrew P. Lentvorski, Jr.
On Wed, 3 Sep 2003, Malcolm Tredinnick wrote: My only real request is to continue supporting Python 2.2. I was one of the people in favour of requiring 2.2 early on, so this risks sounding hypocritical, but the changes between 2.2 and 2.3 are not as large as from 2.1 to 2.2 and there will be

Re: [pygtk] CVS branches and plans for the future.

2003-09-06 Thread James Henstridge
On 06/09/03 14:58, Andrew P. Lentvorski, Jr. wrote: On Wed, 3 Sep 2003, Malcolm Tredinnick wrote: My only real request is to continue supporting Python 2.2. I was one of the people in favour of requiring 2.2 early on, so this risks sounding hypocritical, but the changes between 2.2 and 2.3

Re: [pygtk] CVS branches and plans for the future.

2003-09-06 Thread Andrew P. Lentvorski, Jr.
On Sat, 6 Sep 2003, James Henstridge wrote: Since when will GTK 2.4 break binary compatibility? Well, I think my impression about that came from discussions originating in this thread where Owen talks about new API in 2.4: http://www.geocrawler.com/mail/msg.php3?msg_id=10282211list=521

Re: [pygtk] CVS branches and plans for the future.

2003-09-03 Thread Malcolm Tredinnick
On Wed, 2003-09-03 at 19:19, James Henstridge wrote: On 3/09/2003 9:50 AM, Malcolm Tredinnick wrote: [...] What do you think about moving the gtksourceview bindings into the main module (I'm not sure where exactly in the directory tree)? This is all said without having talked to the maintainer

[pygtk] CVS branches and plans for the future.

2003-09-02 Thread James Henstridge
I have just branched pygtk, pyorbit and gnome-python in CVS. If you want to get the 2.0 branches, you will need to switch your branches over to the branches: cd pygtk; cvs update -r pygtk-2-0 . cd pyorbit; cvs update -r pyorbit-2-0 . cd gnome-python; cvs update -r gnome-python-2-0 .

Re: [pygtk] CVS branches and plans for the future.

2003-09-02 Thread Malcolm Tredinnick
On Wed, 2003-09-03 at 00:46, James Henstridge wrote: I have just branched pygtk, pyorbit and gnome-python in CVS. If you want to get the 2.0 branches, you will need to switch your branches over to the branches: cd pygtk; cvs update -r pygtk-2-0 . cd pyorbit; cvs update -r

Re: [pygtk] CVS branches and plans for the future.

2003-09-02 Thread Christian Reis
On Wed, Sep 03, 2003 at 11:50:41AM +1000, Malcolm Tredinnick wrote: Any comments? My only real request is to continue supporting Python 2.2. I was one of Seconded, for similar reasons as Malcolm's. Take care, -- Christian Reis, Senior Engineer, Async Open Source, Brazil.