Python 2.3.5 ?

[Luis M. Gonzalez]

I'm confussed...
Python 2.4 (final) hs been released a few days ago, but now I see that
Python 2.3.5 is being worked on.
Why? What does it mean?

[Larry Bates]

Just because 2.4 arrives doesn't mean that ALL work is stopped
on 2.3. It is quite common to have releases overlap. The very
newest release is put out (2.4) , but bugs are still being fixed
in older (2.3).

Larry Bates

Luis M. Gonzalez wrote:

I'm confussed...
Python 2.4 (final) hs been released a few days ago, but now I see that
Python 2.3.5 is being worked on.
Why? What does it mean?

[Tim Peters]

[Luis M. Gonzalez]

I'm confussed...
Python 2.4 (final) hs been released a few days ago, but now I
see that Python 2.3.5 is being worked on.
Why? What does it mean?

Just that enough volunteers exist interested in producing another
bugfix release for the 2.3 line. It will probably be the last in the
2.3 line. Heck, if enough volunteers showed up for it, we could have
a 1.5.3 release too. Not everyone is willing and able to switch to a
new 2.j release as soon as it appears. So far nobody has been willing
to pay to keep the 2.(j-1) line going, but it's quite common for
volunteers to supply a new & last bugfix release in the 2.(j-1) line
near the time 2.j final is released.

If you don't have a need to stick with 2.3 (where "need" can include
orders from corporate management), of course I recommend moving to
2.4.

[It's me]

Not to mention that there are packages out there that doesn't work (yet)
with 2.4. Pynum is one such package.

--
It's me
"Larry Bates" <lb****@syscono nline.com> wrote in message
news:Ns******** ************@co mcast.com...

Just because 2.4 arrives doesn't mean that ALL work is stopped
on 2.3. It is quite common to have releases overlap. The very
newest release is put out (2.4) , but bugs are still being fixed
in older (2.3).

Larry Bates

Luis M. Gonzalez wrote:

I'm confussed...
Python 2.4 (final) hs been released a few days ago, but now I see that
Python 2.3.5 is being worked on.
Why? What does it mean?

[Stefan Behnel]

Stefan

mails!
the way you read
it doesn't reflect
why top-posting is bad:
It's me wrote:

Not to mention that there are packages out there that doesn't work (yet)
with 2.4. Pynum is one such package.

--
It's me
"Larry Bates" <lb****@syscono nline.com> wrote in message
news:Ns******** ************@co mcast.com...

Just because 2.4 arrives doesn't mean that ALL work is stopped
on 2.3. It is quite common to have releases overlap. The very
newest release is put out (2.4) , but bugs are still being fixed
in older (2.3).

Larry Bates

Luis M. Gonzalez wrote:

I'm confussed...
Python 2.4 (final) hs been released a few days ago, but now I see that
Python 2.3.5 is being worked on.
Why? What does it mean?

[Fuzzyman]

Fuzzy

Regards,
What's that phrase that includes 'hobgoblin of little minds' ?

[Peter Hansen]

Fuzzyman wrote:

What's that phrase that includes 'hobgoblin of little minds' ?

It's about "foolish consistency", but I don't see the relevance
to the current thread.

Are you suggesting that back-porting bug fixes to older
versions of Python is foolish?

-Peter

[Fuzzyman]

Hello Peter,

Sorry to confuse you. It was actually a reply to Stefans dig about top
posting.

Regards,

Fuzzy

[Peter Hansen]

Fuzzyman wrote:

Hello Peter,

Sorry to confuse you. It was actually a reply to Stefans dig about top
posting.

Hmm... I don't even see any named Stefan posting in this thread.
I hope my newsreader isn't dropping messages... :-(

Anyway, not important, never mind.

-Peter

[Brad Tilley]

Tim Peters wrote:

Not everyone is willing and able to switch to a
new 2.j release as soon as it appears.

The reason I jumped on 2.4 right away was the msi installer for Windows
systems. We can do unattended/automated installs... it's really great...
a killer feature for Windows users who need to install Python on lots of
machines.

Bye