Stefan Spoettl wrote:
In the pass it was always a good idea to use the newest Python verison
for starting the development of a new application. First one could
benefit from the additional features and second one could be sure that
the community would have been passing during development.
Nowa
On Mar 6, 1:23 pm, "andrew cooke" wrote:
> 3 and 2.6 are compatible. so develop on 3, to make sure you don't use old
> junk, and then switch to 2.6 if you need to. there are a few wrinkles in
> doing so, but it is not a big problem.
>
> 3.0 is a nicer language. it's cleaner and more consistent.
3 and 2.6 are compatible. so develop on 3, to make sure you don't use old
junk, and then switch to 2.6 if you need to. there are a few wrinkles in
doing so, but it is not a big problem.
3.0 is a nicer language. it's cleaner and more consistent. i think
important libraries will move there. no
In the pass it was always a good idea to use the newest Python verison for
starting the development of a new application. First one could benefit from the
additional features and second one could be sure that the community would have
been passing during development.
Nowadays we have at least th
