What is the role of python2.6 and C++?

[Ìð¹Ï]

Howdy,

I'm confused about the motivation of releasing python2.6 and python3.0
at the *same* time. IMO, 2.6 should be compatible with 2.5 while 3.0
is new style python. Currenly, most python projects works fine in 2.5.
When 3.0 becomes final release, those projects will be gradually moved
to 3.0. But even without the intermediate version 2.6, project
transformation with be smooth enough, and then 2.5, 2.6 will be
replaced by 3.0. I will not spend any time on studying 2.6. So why
does python development team put many efforts on 2.6? What is the role
of 2.6?

Another question is about the future of C++. I am a C++ programmer.
Since I studied python, most of my projects becomes written in python
because of the better and simpler OOP representation. As a supplement,
I use python C extension for computational extensive jobs. Therefore,
for a relatively long time, I do not use C++ any more... Anyone is
same to me? What is your attitude to the role of C++ in the age of
python?

Best regards,

 

[cokofreedom]

Howdy,

I'm confused about the motivation of releasing python2.6 and python3.0
at the *same* time. IMO, 2.6 should be compatible with 2.5 while 3.0
is new style python. Currenly, most python projects works fine in 2.5.
When 3.0 becomes final release, those projects will be gradually moved
to 3.0. But even without the intermediate version 2.6, project
transformation with be smooth enough, and then 2.5, 2.6 will be
replaced by 3.0. I will not spend any time on studying 2.6. So why
does python development team put many efforts on 2.6? What is the role
of 2.6?

Best regards,

2.6 is meant to be a continuation of the 2.x line of Python, to
support a gradual move of larger projects over to the Python 3.x
series. The idea is that as Python 3.x will cause some major and minor
changes to the basics of Python as we currently know it, trying to
move everyone straight away will be problematic.

Therefore the point is there will be a 2.7, 2.8 and so forth until
there is almost no difference between
the 2.x and 3.x at which time most users will have moved to the 3.x
series and the 2.x can be discontinued.

I will program larger projects in 2.5 for a while and then perhaps
look to move it to 2.6 and 2.7, I won't touch the 3.x series until it
is the common choice, much as a lot of people still program in 2.3/4.

 

[Marc 'BlackJack' Rintsch]

I'm confused about the motivation of releasing python2.6 and python3.0
at the *same* time. IMO, 2.6 should be compatible with 2.5 while 3.0
is new style python.

That's how it is. 2.6 is backwards compatible with 2.5.

[…] But even without the intermediate version 2.6, project transformation
with be smooth enough, and then 2.5, 2.6 will be replaced by 3.0. I will
not spend any time on studying 2.6. So why does python development team
put many efforts on 2.6? What is the role of 2.6?

It's a version that makes the transition smoother. You really should take
that "detour" via 2.6. There should be some of the changes from 3.0 in 2.6
that don't mess with backwards compatibility, and a script that tries to
automate the conversion from 2.6 to 3.0. This spares a lot of work when
porting to 3.0.

Ciao,
Marc 'BlackJack' Rintsch

 

[Ìð¹Ï]

I will program larger projects in 2.5 for a while and then perhaps

look to move it to 2.6 and 2.7, I won't touch the 3.x series until it
is the common choice, much as a lot of people still program in 2.3/4.

Oh, I see. It seems the gap between 2.5 and 3.0 is not so small.
Therefore, even if 3.0 is released, it may take many months for
porting old projects.
I agree with you to wait until python 3.0 becomes common choice. Hope
this day comes as soon as possible.

 

[Fredrik Lundh]

2.6 is meant to be a continuation of the 2.x line of Python, to
support a gradual move of larger projects over to the Python 3.x
series.

note that Python also has a tradition of releasing X.6 and (X+1).0 at
the same time:

http://mail.python.org/pipermail/python-announce-list/2000-September/000513.html
http://mail.python.org/pipermail/python-list/2000-September/051263.html

</F>

 

[Ulrich Eckhardt]

Another question is about the future of C++. I am a C++ programmer.
Since I studied python, most of my projects becomes written in python
because of the better and simpler OOP representation. As a supplement,
I use python C extension for computational extensive jobs. Therefore,
for a relatively long time, I do not use C++ any more... Anyone is
same to me? What is your attitude to the role of C++ in the age of
python?

I guess the key here is "agile programming". Python allows you to quickly
change things, sometimes even on the fly and test them using the
interpreter. C++ offers high performance while still providing a high-level
interface. In fact using Boost.Python, it is even a piece of cake to
integrate C++ code into Python, including automatic conversion of things
like std::string or exceptions.

My personal feeling is that neither of the two is going away, last but not
least because of the large amounts of existing C and C++ code.

Uli