Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Kegan
I have just started using 2.6 (upgrade from 2.5). All my web
applications' code (using Django), work without any changes.
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Steven D'Aprano
On Sat, 12 Sep 2009 20:25:47 -0700, Kee Nethery wrote:

 I would prefer to be in 3.x because all the inconsistencies of how you
 do things in 2.x make it harder than it needs to be to learn the
 language.
 
 People who have been coding in 2.x for along time don't notice how the
 syntax is wonky in places. Their fingers type the right stuff. As a
 newbie I assume that everything works the same way and I am frequently
 surprised.

What inconsistencies surprise you?



-- 
Steven
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Peng Yu
On Sun, Sep 13, 2009 at 12:27 AM, John Nagle na...@animats.com wrote:
 Kee Nethery wrote:

 I am in 2.x because the IDE I am using does not support stepping through
 my code when in 3.x. As soon as the IDE I use supports debugging in 3.x, I'm
 moving up to 3.x.

 I would prefer to be in 3.x because all the inconsistencies of how you do
 things in 2.x make it harder than it needs to be to learn the language.

   So would I.  But the infrastructure isn't there yet.  Realistically,
 2.5 is the production stable version of CPython.  Almost all important
 modules work with CPython 2.5.  Some work with 2.6.  3.x support remains
 spotty.  Give it a year.  Or two.

   I've tried using 3.1, but had to back down.

What are the differences between 2.5 and 2.6?
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Andreas Waldenburger
On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu pengyu...@gmail.com wrote:

 On Sun, Sep 13, 2009 at 12:27 AM, John Nagle na...@animats.com
 wrote:
 What are the differences between 2.5 and 2.6?

http://docs.python.org/dev/whatsnew/2.6.html

/W

-- 
INVALID? DE!

-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Peng Yu
On Sun, Sep 13, 2009 at 4:01 PM, Andreas Waldenburger
use...@geekmail.invalid wrote:
 On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu pengyu...@gmail.com wrote:

 On Sun, Sep 13, 2009 at 12:27 AM, John Nagle na...@animats.com
 wrote:
 What are the differences between 2.5 and 2.6?

 http://docs.python.org/dev/whatsnew/2.6.html

Are all packages available in 2.5 also available in 2.6?

Regards,
Peng
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-13 Thread Andreas Waldenburger
On Sun, 13 Sep 2009 17:04:25 -0500 Peng Yu pengyu...@gmail.com wrote:

 On Sun, Sep 13, 2009 at 4:01 PM, Andreas Waldenburger
 use...@geekmail.invalid wrote:
  On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu pengyu...@gmail.com
  wrote:
 
  On Sun, Sep 13, 2009 at 12:27 AM, John Nagle na...@animats.com
  wrote:
  What are the differences between 2.5 and 2.6?
 
  http://docs.python.org/dev/whatsnew/2.6.html
 
 Are all packages available in 2.5 also available in 2.6?
 
If the release notes don't say otherwise, then yes.

The general rule is this: *Only* Python 3 breaks backwards
compatibility. If it works in Python 2.n then it will work unmodified
in Python 2.(n+1).

Please note that I'm talking about the *standard library* and the
language itself, of course. Usually newer versions are not as widely
supported as older ones as far as third party modules go.

/W

-- 
INVALID? DE!

-- 
http://mail.python.org/mailman/listinfo/python-list


Which version of python I should use if I just start programming in python?

2009-09-12 Thread Peng Yu
Hi,

I just start python programming. That is, I don't have any legacy
code. I notice that there are different versions of python. I would
guess that older version of python has the more libraries than newer
versions. But the code developed in newer versions might be better
supported in the future. Can somebody give a guideline on which
version of python a new python developer shall choose?

Regards,
Peng
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread Terry Reedy

Peng Yu wrote:

Hi,

I just start python programming. That is, I don't have any legacy
code. I notice that there are different versions of python. I would
guess that older version of python has the more libraries than newer
versions. But the code developed in newer versions might be better
supported in the future. Can somebody give a guideline on which
version of python a new python developer shall choose?


My own view is start with 3.1 and move back to 2.6 or even 2.5 when you 
need a library not available with 3.1. Others will say start with 2.6 or 
2.5. This has been discussed previously on this list.


--
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread r
On Sep 12, 3:47 pm, Peng Yu pengyu...@gmail.com wrote:
 Hi,

 I just start python programming. That is, I don't have any legacy
 code. I notice that there are different versions of python. I would
 guess that older version of python has the more libraries than newer
 versions. But the code developed in newer versions might be better
 supported in the future. Can somebody give a guideline on which
 version of python a new python developer shall choose?

 Regards,
 Peng

Boxers or briefs? ;-)

Well both have pros and cons. As for myself i am using 2.x until it
expires, but that is because i already have much code in 2.x line. If
you are starting from scratch i would say 3.x. The only bad aspect of
2.x right now is that eventually (if you want to keep current) you
will have to make the change to 3.0 and since backwards compatabiltity
is broken you will need to do more than just download the new
version!

At the very least you should learn the 2.x just to see why such
changes were made. But in the end keep all *real* projects in the
Python 3.0. So just lean with 3.0 and if you find some need for 2.x
(3rd party modules) use it for christs sake!

At this point in time with 3rd party modules still converting i would
say 3.0 may feel like a pair of tight briefs and your boys might
start to feel confined shall we say. With 2.x you will feel the free-
ballin' freedom of more choices at your disposal. But eventually the
tides will shift!
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread Peng Yu
On Sep 12, 4:10 pm, Terry Reedy tjre...@udel.edu wrote:
 Peng Yu wrote:
  Hi,

  I just start python programming. That is, I don't have any legacy
  code. I notice that there are different versions of python. I would
  guess that older version of python has the more libraries than newer
  versions. But the code developed in newer versions might be better
  supported in the future. Can somebody give a guideline on which
  version of python a new python developer shall choose?

 My own view is start with 3.1 and move back to 2.6 or even 2.5 when you
 need a library not available with 3.1. Others will say start with 2.6 or
 2.5. This has been discussed previously on this list.

Would you please point me where the previous discussion is?
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread Terry Reedy

Peng Yu wrote:

On Sep 12, 4:10 pm, Terry Reedy tjre...@udel.edu wrote:

Peng Yu wrote:

Hi,
I just start python programming. That is, I don't have any legacy
code. I notice that there are different versions of python. I would
guess that older version of python has the more libraries than newer
versions. But the code developed in newer versions might be better
supported in the future. Can somebody give a guideline on which
version of python a new python developer shall choose?

My own view is start with 3.1 and move back to 2.6 or even 2.5 when you
need a library not available with 3.1. Others will say start with 2.6 or
2.5. This has been discussed previously on this list.


Would you please point me where the previous discussion is?


http://groups.google.com/group/comp.lang.python/topics

type question in search box and click 'search this group'

and see what you get


--
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread Kee Nethery
I am in 2.x because the IDE I am using does not support stepping  
through my code when in 3.x. As soon as the IDE I use supports  
debugging in 3.x, I'm moving up to 3.x.


I would prefer to be in 3.x because all the inconsistencies of how you  
do things in 2.x make it harder than it needs to be to learn the  
language.


People who have been coding in 2.x for along time don't notice how the  
syntax is wonky in places. Their fingers type the right stuff. As a  
newbie I assume that everything works the same way and I am frequently  
surprised. One of the goals of 3.x was to make the language more  
consistent and that would make it easier for us newbies.


Kee
--
http://mail.python.org/mailman/listinfo/python-list


Re: Which version of python I should use if I just start programming in python?

2009-09-12 Thread John Nagle

Kee Nethery wrote:
I am in 2.x because the IDE I am using does not support stepping through 
my code when in 3.x. As soon as the IDE I use supports debugging in 3.x, 
I'm moving up to 3.x.


I would prefer to be in 3.x because all the inconsistencies of how you 
do things in 2.x make it harder than it needs to be to learn the language.


   So would I.  But the infrastructure isn't there yet.  Realistically,
2.5 is the production stable version of CPython.  Almost all important
modules work with CPython 2.5.  Some work with 2.6.  3.x support remains
spotty.  Give it a year.  Or two.

   I've tried using 3.1, but had to back down.

John Nagle
--
http://mail.python.org/mailman/listinfo/python-list