I see tonight on comp.lang.python that there is a new release
of Python 2.2, ie 2.2.3.c1. This is billed as a bugfix of v2.2,
ie many bugs fixed. However, it does list a few changes and
possible obscure code-breakers. The question, of course is:
Is this a good idea for someone currently using Python 2.2.2
with wxPython 2.4.0.7???
I'm guessing that Python 2.3 will be out before too much longer.
Maybe it's better idea to wait for 2.3 than to get 2.2.3, then
2.3. I'm clueless. Suggestions?
Al
I see tonight on comp.lang.python that there is a new release
of Python 2.2, ie 2.2.3.c1. This is billed as a bugfix of v2.2,
It's a *release candidate" for a bug fix release.
ie many bugs fixed. However, it does list a few changes and
possible obscure code-breakers. The question, of course is:
Is this a good idea for someone currently using Python 2.2.2
with wxPython 2.4.0.7???
Are you affected by any of the current Python 2.2 bugs?
It seems extremely unlikely that 2.2.3 would not work with
wxPython for Python 2.2, but unless you have problems with
the current bugs in 2.2.2, I see no reason to change.
I'd certainly wait for the full 2.2.3 release if I wasn't
affected by a current bug or wanted to help weed out possible
remaining bugs in the 2.2.3 release. There is always a risk in
being first at trying something.
I'm guessing that Python 2.3 will be out before too much longer.
Maybe it's better idea to wait for 2.3 than to get 2.2.3, then
2.3. I'm clueless. Suggestions?
The move to 2.3 is a much bigger change. You won't be able
to use your current wxPython binaries with Python 2.3.
···
At 23:27 2003-05-22 -0700, achrist@easystreet.com wrote:
--
Magnus Lycka (It's really Lyckå), magnus@thinkware.se
Thinkware AB, Sweden, www.thinkware.se
I code Python ~ The shortest path from thought to working program
achrist@easystreet.com wrote:
I see tonight on comp.lang.python that there is a new release
of Python 2.2, ie 2.2.3.c1. This is billed as a bugfix of v2.2,
ie many bugs fixed. However, it does list a few changes and
possible obscure code-breakers. The question, of course is:
Is this a good idea for someone currently using Python 2.2.2
with wxPython 2.4.0.7???
One philosphy:
Install 2.2.3.c1, exercise your code extensively this weekend
in hopes of producing release feedback for 2.2.3. If you find
a nasty bug (2.2.[12] vs. 2.2.3c1), they might fix it for 2.2.3,
or even delay 2.2.3 release if they decide the impact is too
substantial. Only do this if you are willing to quickly file
an explicit bug report. The idea is to help test the release.
I'm guessing that Python 2.3 will be out before too much longer.
Maybe it's better idea to wait for 2.3 than to get 2.2.3, then
2.3. I'm clueless. Suggestions?
Sticking to 2.2 (but going to 2.2.3) might be your favorite choice,
since 2.2 (the Py-in-a-Tie version) should outlast 2.3. That is,
big fixes will continue in 2.2 after we are in 2.4, but 2.3 will
be abandoned at that point.
-Scott David Daniels
Scott.Daniels@Acm.Org
I don't understand. When we are in 2.4 why would the Python team
continue to pump out fixes for 2.2 but "abandon", as you say, 2.3?
···
On Saturday 24 May 2003 12:45 pm, Scott David Daniels wrote:
Sticking to 2.2 (but going to 2.2.3) might be your favorite choice,
since 2.2 (the Py-in-a-Tie version) should outlast 2.3. That is,
big fixes will continue in 2.2 after we are in 2.4, but 2.3 will
be abandoned at that point.
--
Chuck
http://ChuckEsterbrook.com
I think the Python Business Forum http://www.python-in-business.org/
and the Snake Farm Snake Farm will have to
take over backporting by then.
The python development team and the Python Business Forum has
discussed the issue of supporting python versions with bugfixes
etc for longer time, to make python more commercially viable in
large istallations where installation cycles of several years are
common. (For instance, one of my current customers is committed
to stay with MS Office 97 for at least two more years.)
So, a decision has been made to make version 2.2 available for a
long time. If 2.4 comes reasonably soon, there will still be
bugfixes made for 2.2, but I suppose 2.3 will be dropped when
2.4 is stable enough. I don't know if an exact lifespan for 2.2
has been decided.
As a consequence, it would be bad to make toolkits like wxPython
depend on Python 2.3 or 2.4 features as long as 2.2 is still
"Python-In-A-Tie".
···
At 13:29 2003-05-24 -0700, Chuck Esterbrook wrote:
I don't understand. When we are in 2.4 why would the Python team
continue to pump out fixes for 2.2 but "abandon", as you say, 2.3?
--
Magnus Lycka (It's really Lyckå), magnus@thinkware.se
Thinkware AB, Sweden, www.thinkware.se
I code Python ~ The shortest path from thought to working program