Re: Which Version Of Python Is Best To Install Now..
On 10/9/20 1:02 AM, Muhammad Saad wrote: > > > > >Sent from [1]Mail for Windows 10 > >I Want To Reinstall Python Now Which Version I Install Now > > References > >Visible links >1. https://go.microsoft.com/fwlink/?LinkId=550986 > The latest, 3.9, is as always considered the "best available" version. But there is no need to upgrade immediately. If you use lots of installed modules you should check if they have "caught up" - if there is actually a 3.9 version available. Popular things like numpy have not yet been released for 3.9. If you do use such packages, you can go to pypi.org and search for the modules you care about - click on Download Files and if there are lots of what look like version/operating system-encoded names like *-cp37-win_amd64.whl, *-cp38-win_amd64.whl, etc. then make sure there are ones with 39 if you want to install 3.9. If not, you'll want to stay with 3.8 for a while. -- https://mail.python.org/mailman/listinfo/python-list
Which Version Of Python Is Best To Install Now..
Sent from [1]Mail for Windows 10 I Want To Reinstall Python Now Which Version I Install Now References Visible links 1. https://go.microsoft.com/fwlink/?LinkId=550986 -- https://mail.python.org/mailman/listinfo/python-list
RE: Which Version of Python?
Ramchandra Apte wrote: > On Wednesday, 12 September 2012 14:11:56 UTC+5:30, Ramchandra Apte wrote: > > On Wednesday, 12 September 2012 14:04:56 UTC+5:30, alex23 wrote: > > > On 12 Sep, 16:31, Mark Lawrence wrote: > > > > Perhaps this will sway youhttp://docs.python.org/dev/whatsnew/3.3.html > > > > There is no longer an equivalent document for the Python 1.x or 2.x > > > > series of releases. > > > Perhaps not for 1.x but the 2.x series is still covered: > > > http://docs.python.org/dev/whatsnew/index.html > > > Actually, 1.6 is included here: > > > http://www.python.org/download/releases/1.6.1/ > > I think he meant the length of the document. > Sorry, Mark must have meant theres no "What's New" document of the same length > (its very long). Would you mind trimming your responses of blank lines? The double line spacing makes it difficult to read. I know that it may be google groups that is doubling line spaces but it would help if you could remove the extra lines that you can when replying (as I have done above). Thanks, Ramit This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
[ Ramchandra Apte wrote on Tue 11.Sep'12 at 19:58:29 -0700 ] > On Tuesday, 11 September 2012 22:19:08 UTC+5:30, Charles Hottel wrote: > > I have a lot of programming experience in many different languages and now > > > > I want to learn Python. Which version do you suggest I download, Python > > 2.x > > > > or Python 3.x ? Also why should I prefer one over the other? > > > > > > > > Right now I am thinkng Python 3.x as it has been out since 2008, but I have > > > > some concerns about backward compatibility with older packages that I might > > > > want to use. > > > > > > > > Thanks for your ideas and help. > > Use Python 3 because most packages support Python 3. Python 2.7 has many > features that Python 3 has so it will require minimal effort to write Python > 2.x code. When I first started to learn Python - about a year ago - I got myself a book which focuses on version 3 but is does also include Version 2. The author wrote that because a number of supporting libraries have not been updated to work in Python 3, and where "it is felt that the theory still needs to be expounded upon" Python 2.x will be used in lieu of Python 3. I personally, as a beginner, have found this approach helpful. Although, when this book was published Python 3.1 was the latest release, so of course since then said libraries most probably have been updated. So, as a fellow beginner i'd go for version 3.x. Jamie. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On Wednesday, 12 September 2012 14:11:56 UTC+5:30, Ramchandra Apte wrote: > On Wednesday, 12 September 2012 14:04:56 UTC+5:30, alex23 wrote: > > > On 12 Sep, 16:31, Mark Lawrence wrote: > > > > > > > Perhaps this will sway youhttp://docs.python.org/dev/whatsnew/3.3.html > > > > > > > There is no longer an equivalent document for the Python 1.x or 2.x > > > > > > > series of releases. > > > > > > > > > > > > Perhaps not for 1.x but the 2.x series is still covered: > > > > > > http://docs.python.org/dev/whatsnew/index.html > > > > > > > > > > > > Actually, 1.6 is included here: > > > > > > http://www.python.org/download/releases/1.6.1/ > > > > I think he meant the length of the document. Sorry, Mark must have meant theres no "What's New" document of the same length (its very long). -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On Wednesday, 12 September 2012 14:04:56 UTC+5:30, alex23 wrote: > On 12 Sep, 16:31, Mark Lawrence wrote: > > > Perhaps this will sway youhttp://docs.python.org/dev/whatsnew/3.3.html > > > There is no longer an equivalent document for the Python 1.x or 2.x > > > series of releases. > > > > Perhaps not for 1.x but the 2.x series is still covered: > > http://docs.python.org/dev/whatsnew/index.html > > > > Actually, 1.6 is included here: > > http://www.python.org/download/releases/1.6.1/ I think he meant the length of the document. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On 12 Sep, 16:31, Mark Lawrence wrote: > Perhaps this will sway youhttp://docs.python.org/dev/whatsnew/3.3.html > There is no longer an equivalent document for the Python 1.x or 2.x > series of releases. Perhaps not for 1.x but the 2.x series is still covered: http://docs.python.org/dev/whatsnew/index.html Actually, 1.6 is included here: http://www.python.org/download/releases/1.6.1/ -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On 11/09/2012 17:49, Charles Hottel wrote: I have a lot of programming experience in many different languages and now I want to learn Python. Which version do you suggest I download, Python 2.x or Python 3.x ? Also why should I prefer one over the other? Right now I am thinkng Python 3.x as it has been out since 2008, but I have some concerns about backward compatibility with older packages that I might want to use. Thanks for your ideas and help. Perhaps this will sway you http://docs.python.org/dev/whatsnew/3.3.html There is no longer an equivalent document for the Python 1.x or 2.x series of releases. -- Cheers. Mark Lawrence. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
I try to usually use several versions to know the difference. You never
know when a package might come along, and you want to try it out, and then
version becomes compatibility.
Alternatively, a client might come along and insist that a particular
version be used.
Do a little quick research on the differences, and try them out. You might
want to know a few things like from __future__ import x for the 2's or
print 'this' become print('this') in later ones, etc.
--
Best Regards,
David Hutto
*CEO:* *http://www.hitwebdevelopment.com*
--
http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On Tuesday, 11 September 2012 22:19:08 UTC+5:30, Charles Hottel wrote: > I have a lot of programming experience in many different languages and now > > I want to learn Python. Which version do you suggest I download, Python 2.x > > or Python 3.x ? Also why should I prefer one over the other? > > > > Right now I am thinkng Python 3.x as it has been out since 2008, but I have > > some concerns about backward compatibility with older packages that I might > > want to use. > > > > Thanks for your ideas and help. Use Python 3 because most packages support Python 3. Python 2.7 has many features that Python 3 has so it will require minimal effort to write Python 2.x code. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On Wed, 12 Sep 2012 02:11:22 +, Steven D'Aprano wrote: > On Tue, 11 Sep 2012 17:17:14 -0700, Peter wrote: > >> If your desire is to "learn" Python then I would stick to 2.7 >> >> My reasoning would be that there are still a significant number of >> packages that have not been ported to 3.x (and may never be ported). > > But if all you want is to learn Python, then those packages are > irrelevant. If I want to learn to write Python code, why should I care > about SomePackage, regardless of whether it supports Python 3.x or 2.x > or even 1.x? As a beginner to the language, I don't even know it exists, > and chances are I'm never going to use it. > > (I was happily using Python using only the standard library for about > seven years before I installed my first third-party library.) > > You may not have intended it this way, but the argument "stick to Python > 2, because packages!" is a typical troll response. It might have been a > reasonable response six years ago, when there weren't many (or even any) > major packages that supported Python 3, Hardly surprising given that Python 3 came out four years ago. Sorry, brain-fart. I meant four years ago. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On Tue, 11 Sep 2012 17:17:14 -0700, Peter wrote: > If your desire is to "learn" Python then I would stick to 2.7 > > My reasoning would be that there are still a significant number of > packages that have not been ported to 3.x (and may never be ported). But if all you want is to learn Python, then those packages are irrelevant. If I want to learn to write Python code, why should I care about SomePackage, regardless of whether it supports Python 3.x or 2.x or even 1.x? As a beginner to the language, I don't even know it exists, and chances are I'm never going to use it. (I was happily using Python using only the standard library for about seven years before I installed my first third-party library.) You may not have intended it this way, but the argument "stick to Python 2, because packages!" is a typical troll response. It might have been a reasonable response six years ago, when there weren't many (or even any) major packages that supported Python 3, but now many major packages do and most of those that don't are in the process of doing so. Now the choice is, paradoxically, much harder because library support is much more split: some libraries support 2.x, some 3.x, and some both. Of course, if you *need* to use SomePackage which only supports Python 2 or 3, then that will drive your decision to learn Python 2 or 3. But consider: (1) If a package only supports Python 2 now, and *has no plans* to support Python 3, I would consider that package more or less a dead end and be reluctant to start a new project with it unless I had no other choice at all. (Seriously guys, if you're the developer of a project that only supports 2.x and you aren't at least *thinking about* supporting 3.x, your project is going to be irrelevant to the wider world soon.) (2) The syntax differences between Python 2 and 3 are very minor. By the time you are proficient in one, you will be *easily* be able to jump to the other. > Not having looked at the changes in 3.x (so don't flame me! :-)), it > would seem that anything you "learn" in 2.7 would be easily transferred > "up" when and if you feel the need to go to 3.x, It goes both ways. But frankly, whenever I drop down from 3.x code to 2.x code, I get really annoyed that there's a lot of excellent stuff I cannot use. > but in the meantime > enjoy the better support of a greater range of packages that are still > only 2.x compatible! That's true. But the range of 3.x compatible third party libraries is very impressive: it includes numpy and scipy, CherryPy, parts of zope (but not yet all of it), pyparsing, an unofficial port of nltk, py2exe, and many more. Others, like django, have committed to support 3.x as soon as they can drop support for 2.4 or 2.5. See also: http://python3wos.appspot.com/ PyPy is now in the process of supporting Python 3. Within a few years, Python 3 will be the standard. > i.e. learning (and using) features of 3.x could > make it difficult to go "down" when/if you decide you really need to use > a library that hasn't (and may never!) be ported to 3.x. Any package that is not ported to 3.x will eventually be as obsolete and irrelevant as packages that only support Python 1.5. Python 2.7 will have an extended support period, but that won't last forever. My estimate is that we're past the half-way mark: in another four years, the question of "2.x or 3.x" will be irrelevant, people will be asking "I want to use library foo, but it only supports 2.7, what should I do?", and in eight years, people won't even ask that, they'll just ignore library foo as abandoned. > So in this case, staying with the lower common denominator might be the > better choice. Everyone has to make that choice for themselves, based on what libraries they intend to use. For those who don't intend to use any libraries at all, I think the answer is simple: Learn the version of Python that comes installed on your computer, or if you have to install it yourself, learn Python 3. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On 2012.09.11 19:17, Peter wrote: > If your desire is to "learn" Python then I would stick to 2.7 > > My reasoning would be that there are still a significant number of packages > that have not been ported to 3.x (and may never be ported). This is true, but the /potential/ for the need for one of these packages is not a good reason to learn from a branch that will never get any new features. If there is indeed a compelling reason to stay with the older version, then it is a worthwhile tradeoff. Otherwise, it is just silly. > Not having looked at the changes in 3.x (so don't flame me! :-)) That would be a good reason /to/ flame you. ;) > , it would seem that anything you "learn" in 2.7 would be easily transferred > "up" when and if you feel the need to go to 3.x, 3.x is not a simple superset of 2.7 - there are certain limitations and ways of doing things in 2.x that don't apply to 3.x. A new programmer should learn, for example, handling Unicode properly (which is strongly encouraged in 3.x) and then learn how to deal with less-than-ideal implementations (like 2.x) rather than learn how to do it sloppily and then be frustrated when 3.x wants them to do it correctly. Backward compatibility was not broken for trivial reasons. > i.e. learning (and using) features of 3.x could make it difficult to go "down" The official documentation does point out things that have been added/changed both overall in the "What's New" page and specifically in each module's documentation. > when/if you decide you really need to use a library that hasn't (and may > never!) be ported to 3.x. I don't think it's a good idea to encourage people (especially newbies) to stick with packages that won't get updated. I'm not saying that a package that isn't planned to be 3.x compatible will necessarily be unmaintained, but being unmaintained is the reason many packages will not be made 3.x compatible. In any case, packages that aren't getting support for 3.x will likely be replaced with better alternatives, especially once people start flocking en masse to 3.x (I'm no expert, but my guess is that this will happen once Django and Twisted support 3.x). If 3.0 had come out a month ago, I would see value in learning 2.x, but it's been nearly 4 years. -- CPython 3.3.0b1 | Windows NT 6.1.7601.17803 -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
If your desire is to "learn" Python then I would stick to 2.7 My reasoning would be that there are still a significant number of packages that have not been ported to 3.x (and may never be ported). Not having looked at the changes in 3.x (so don't flame me! :-)), it would seem that anything you "learn" in 2.7 would be easily transferred "up" when and if you feel the need to go to 3.x, but in the meantime enjoy the better support of a greater range of packages that are still only 2.x compatible! i.e. learning (and using) features of 3.x could make it difficult to go "down" when/if you decide you really need to use a library that hasn't (and may never!) be ported to 3.x. For example, Graysons book on Python GUI programming is still one of the better Python GUI books (although very old now!) and it would steer you towards using the Pmw library - which may never be ported to 3.x. If you decide to use wxPython for your GUI work then I see that has support for 2.x only also. So in this case, staying with the lower common denominator might be the better choice. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
"Charles Hottel" writes: > I have a lot of programming experience in many different languages and now > I want to learn Python. Good for you, and welcome! > Which version do you suggest I download, Python 2.x or Python 3.x ? > Also why should I prefer one over the other? This question is a good one. It is common enough that the home page http://www.python.org/> has a link to the community's answer/discussion at http://wiki.python.org/moin/Python2orPython3>. > Right now I am thinkng Python 3.x as it has been out since 2008, but I > have some concerns about backward compatibility with older packages > that I might want to use. The fact that Python 3 has been out for a number of years is important, as is the fact that the Python developers and the community of third-party library developers have worked quite hard to make it feasible to work in Python 3. More important, from the perspective of a newcomer, is that Python 2 is essentially in maintenance-only mode, receiving only bug fixes. All larger improvements are only going into Python 3. The set of third-party libraries which are not ready for Python 3 still has some significant members, and will certainly never be zero. But that set has shrunk significantly in the many years that Python 3 has been active. At this stage, I would advise any person wanting to learn Python qua Python (i.e. without considering the wrinkles of some specific task) to focus on Python 3. If you need to learn older versions, that need will present itself and you can learn the legacy quirks then; for now, learn Python the way it is intended to be by going for Python 3. -- \ “A lie can be told in a few words. Debunking that lie can take | `\ pages. That is why my book… is five hundred pages long.” —Chris | _o__)Rodda, 2011-05-05 | Ben Finney -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
On 11/09/2012 17:49, Charles Hottel wrote: I have a lot of programming experience in many different languages and now I want to learn Python. Which version do you suggest I download, Python 2.x or Python 3.x ? Also why should I prefer one over the other? Right now I am thinkng Python 3.x as it has been out since 2008, but I have some concerns about backward compatibility with older packages that I might want to use. Thanks for your ideas and help. My own preference is for Python 3.x. Python 2.x is ending at 2.7. As you said, some older packages may still be using 2.x, but there's not that much difference between 3.x and 2.x, so you should be able to switch from one to the other one very easily. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which Version of Python?
Having recently looked for the same answer myself, consensus seems to be that you should work with 3.x unless you know you need something that is still 2.x specific. For me, that 2.x specific item was OpenStack. On Tue, Sep 11, 2012 at 12:49 PM, Charles Hottel wrote: > I have a lot of programming experience in many different languages and now > I want to learn Python. Which version do you suggest I download, Python > 2.x > or Python 3.x ? Also why should I prefer one over the other? > > Right now I am thinkng Python 3.x as it has been out since 2008, but I have > some concerns about backward compatibility with older packages that I might > want to use. > > Thanks for your ideas and help. > > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
Which Version of Python?
I have a lot of programming experience in many different languages and now I want to learn Python. Which version do you suggest I download, Python 2.x or Python 3.x ? Also why should I prefer one over the other? Right now I am thinkng Python 3.x as it has been out since 2008, but I have some concerns about backward compatibility with older packages that I might want to use. Thanks for your ideas and help. -- http://mail.python.org/mailman/listinfo/python-list
Re: Which version of python I should use if I just start programming in python?
On Sun, 13 Sep 2009 17:04:25 -0500 Peng Yu wrote: > On Sun, Sep 13, 2009 at 4:01 PM, Andreas Waldenburger > wrote: > > On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu > > wrote: > > > >> On Sun, Sep 13, 2009 at 12:27 AM, John Nagle > >> 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
Re: Which version of python I should use if I just start programming in python?
On Sun, Sep 13, 2009 at 4:01 PM, Andreas Waldenburger wrote: > On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu wrote: > >> On Sun, Sep 13, 2009 at 12:27 AM, John Nagle >> 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?
On Sun, 13 Sep 2009 15:52:44 -0500 Peng Yu wrote: > On Sun, Sep 13, 2009 at 12:27 AM, John Nagle > 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?
On Sun, Sep 13, 2009 at 12:27 AM, John Nagle 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?
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?
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?
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
Re: Which version of python I should use if I just start programming in python?
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?
Peng Yu wrote: On Sep 12, 4:10 pm, Terry Reedy 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?
On Sep 12, 4:10 pm, Terry Reedy 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?
On Sep 12, 3:47 pm, 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? > > 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?
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
Which version of python I should use if I just start programming in python?
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
