Developing for Python (2.x or 3)?
Cameron Laird
claird at lairds.us
Tue Oct 21 14:52:26 EDT 2008
More information about the Python-list mailing list
Tue Oct 21 14:52:26 EDT 2008
- Previous message (by thread): Developing for Python (2.x or 3)?
- Next message (by thread): Developing for Python (2.x or 3)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <9d91714e-47a7-43d1-b380-e0b24d3aabc4 at x1g2000prh.googlegroups.com>, Sean DiZazzo <half.italian at gmail.com> wrote: >I would use 2.5.2 or 2.6. I don't think 3 is anywhere near stable >yet. > >Paulo J. Matos wrote: >> Hi all, >> >> I am in the process of choosing which Python version for a brand new >> application. Van Rossum in an interview recently advised all new >> applications to use Python3 but I am afraid, most libraries (PyGtk, >> PyQt, Networking Libs, etc) won't follow suit to 3.0 and I will end up >> using a version of the language which can't connect to libraries because >> they haven't been ported yet. >> >> Should this be a concern? . . . Forget "stability"; for me, library availability is a far greater consideration. My advice to Mr. Matos is that he is quite right to be concerned about library availability. In fact, there are significant libraries which remain back at 2.5 ... If Mr. Matos happens to know the specific libraries he'll need, and those happen to be on a path to availability for 3.0 soon, of course, my recommendation changes.
- Previous message (by thread): Developing for Python (2.x or 3)?
- Next message (by thread): Developing for Python (2.x or 3)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list