Re: Python 3.x adoption

2014-01-21 Thread Chris Angelico
On Wed, Jan 22, 2014 at 6:04 AM, Travis Griggs wrote: > I’ve had a bunch of interns around me lately though, wanting to get into > python, and this is where I find the momentum really breaks down. If > newcomers go to take an online course in python, they might try MIT’s Open > Courseware (who

Re: Python 3.x adoption

2014-01-21 Thread Chris Kaynor
On Tue, Jan 21, 2014 at 11:04 AM, Travis Griggs wrote: > Being a fan of JIT, I have big hopes for PyPy, I can’t figure out why they > aren’t pitching their “cutting edge” interpreter, for the “cutting edge” > version of python. There should be a wall of superpowers/shame for > interpreters. A ve

Re: Python 3.x adoption

2014-01-21 Thread Travis Griggs
Looks like the 2/3 topic has lain fallow for a couple of days, gotta keep it burning… I’m a relatively recent python convert, but been coding and talking to others about coding for many moons on this big blue orb. I think the industrial side of this debate has been talked up quite a bit. We ha

Re: Python 3.x adoption

2014-01-18 Thread beliavsky
On Friday, January 17, 2014 6:03:45 PM UTC-5, Terry Reedy wrote: > On 1/17/2014 5:16 PM, beliav...@aol.com wrote: > > Python 2 and 3 are incompatible in ways that do not apply to Fortran > > > standards pre- and post- F77. > > > > As stated above, I disagree with respect to pre-F77 and F77

Re: Python 3.x adoption

2014-01-17 Thread Roy Smith
In article , Grant Edwards wrote: > On 2014-01-17, Tim Chase wrote: > > On 2014-01-17 15:27, Grant Edwards wrote: > >> > What's wrong?... > >> > >> Python 2.7 still does everything 99% of us need to do, and we're too > >> lazy to switch. > > > > And in most distros, typing "python" invokes 2

Re: Python 3.x adoption

2014-01-17 Thread Ben Finney
Ben Finney writes: > Terry Reedy writes: > > > Since 3.0, we have added new syntax ('yield from', u'' for instance) > > but I do not believe we have deleted or changed any syntax (I might > > have forgotten something minor) > > I'm aware of the removal of ‘`foo`’ (use ‘repr(foo)’ instead), and >

Re: Python 3.x adoption

2014-01-17 Thread Ben Finney
Terry Reedy writes: > Since 3.0, we have added new syntax ('yield from', u'' for instance) > but I do not believe we have deleted or changed any syntax (I might > have forgotten something minor) I'm aware of the removal of ‘`foo`’ (use ‘repr(foo)’ instead), and removal of ‘except ExcClass, exc_i

Re: Python 3.x adoption

2014-01-17 Thread Chris Angelico
On Sat, Jan 18, 2014 at 10:12 AM, MRAB wrote: > On 2014-01-17 23:03, Terry Reedy wrote: > [snip] > >> Since 3.0, we have added new syntax ('yield from', u'' for instance) but >> I do not believe we have deleted or changed any syntax (I might have >> forgotten something minor) and I do not know of

Re: Python 3.x adoption

2014-01-17 Thread MRAB
On 2014-01-17 23:03, Terry Reedy wrote: [snip] Since 3.0, we have added new syntax ('yield from', u'' for instance) but I do not believe we have deleted or changed any syntax (I might have forgotten something minor) and I do not know of any proposal to do so (except to re-delete u'', which should

Re: Python 3.x adoption

2014-01-17 Thread Terry Reedy
On 1/17/2014 5:16 PM, beliav...@aol.com wrote: I don't think the Fortran analogy is valid. The appropriate analogy for the changes between Python 2.x and 3.x, which started about 1 and 2 decades after the original Python, are the changes between Fortran IV/66 and Fortran 77, also about 1 and

Re: Python 3.x adoption

2014-01-17 Thread Mark Lawrence
On 17/01/2014 22:16, beliav...@aol.com wrote: On Tuesday, January 14, 2014 2:38:29 PM UTC-5, Skip Montanaro wrote: What's the problem with Python 3.x? It was first released in 2008, but web hosting companies still seem to offer Python 2.x rather. For example, Google App Engine only off

Re: Python 3.x adoption

2014-01-17 Thread beliavsky
On Tuesday, January 14, 2014 2:38:29 PM UTC-5, Skip Montanaro wrote: > > What's the problem with Python 3.x? It was first released in 2008, but > > > web hosting companies still seem to offer Python 2.x rather. > > > > > > For example, Google App Engine only offers Python 2.7. > > > > > > What

Re: Python 3.x adoption

2014-01-17 Thread Terry Reedy
On 1/17/2014 10:27 AM, Grant Edwards wrote: On 2014-01-14, Staszek wrote: What's the problem with Python 3.x? The problem with Python 3.x is Python 2.7. ;) Cute. What's wrong?... Python 2.7 still does everything 99% of us need to do, and we're too lazy to switch. While '99' is rhetor

Re: Python 3.x adoption

2014-01-17 Thread Grant Edwards
On 2014-01-17, Tim Chase wrote: > On 2014-01-17 15:27, Grant Edwards wrote: >> > What's wrong?... >> >> Python 2.7 still does everything 99% of us need to do, and we're too >> lazy to switch. > > And in most distros, typing "python" invokes 2.x, and explicitly > typing "python3" is almost 17% l

Re: Python 3.x adoption

2014-01-17 Thread Mark Lawrence
On 17/01/2014 16:15, Tim Chase wrote: On 2014-01-17 15:27, Grant Edwards wrote: What's wrong?... Python 2.7 still does everything 99% of us need to do, and we're too lazy to switch. And in most distros, typing "python" invokes 2.x, and explicitly typing "python3" is almost 17% longer. We're

Re: Python 3.x adoption

2014-01-17 Thread Tim Chase
On 2014-01-17 15:27, Grant Edwards wrote: > > What's wrong?... > > Python 2.7 still does everything 99% of us need to do, and we're too > lazy to switch. And in most distros, typing "python" invokes 2.x, and explicitly typing "python3" is almost 17% longer. We're a lazy bunch! :-) -tkc --

Re: Python 3.x adoption

2014-01-17 Thread Grant Edwards
On 2014-01-14, Staszek wrote: > What's the problem with Python 3.x? The problem with Python 3.x is Python 2.7. ;) > What's wrong?... Python 2.7 still does everything 99% of us need to do, and we're too lazy to switch. -- Grant Edwards grant.b.edwardsYow! We have DIFFERE

Re: Python 3.x adoption

2014-01-16 Thread Piet van Oostrum
Travis Griggs writes: > Personally, I wish they’d start python4, sure would take the heat out of > the 3 vs 2 debates. And maybe there’d be a program called twentyfour as > a result. twelve would be sufficient, I would think. -- Piet van Oostrum WWW: http://pietvanoostrum.com/ PGP key: [8DAE14

Re: Python 3.x adoption

2014-01-15 Thread Christopher Welborn
On 01/14/2014 01:33 PM, Staszek wrote: Hi What's the problem with Python 3.x? It was first released in 2008, but web hosting companies still seem to offer Python 2.x rather. For example, Google App Engine only offers Python 2.7. What's wrong?... My last two hosts have offered multiple versi

Re: Python 3.x adoption

2014-01-15 Thread Chris Angelico
On Thu, Jan 16, 2014 at 3:46 AM, Mark Lawrence wrote: > On 15/01/2014 16:14, Chris Angelico wrote: >> >> On Thu, Jan 16, 2014 at 2:43 AM, Travis Griggs >> wrote: >>> >>> Personally, I wish they’d start python4, sure would take the heat out of >>> the 3 vs 2 debates. And maybe there’d be a program

Re: Python 3.x adoption

2014-01-15 Thread Mark Lawrence
On 15/01/2014 16:14, Chris Angelico wrote: On Thu, Jan 16, 2014 at 2:43 AM, Travis Griggs wrote: Personally, I wish they’d start python4, sure would take the heat out of the 3 vs 2 debates. And maybe there’d be a program called twentyfour as a result. Learn All Current Versions of Python in

Re: Python 3.x adoption

2014-01-15 Thread Chris Angelico
On Thu, Jan 16, 2014 at 2:43 AM, Travis Griggs wrote: > Personally, I wish they’d start python4, sure would take the heat out of the > 3 vs 2 debates. And maybe there’d be a program called twentyfour as a result. Learn All Current Versions of Python in Twenty-Four Hours? ChrisA -- https://mail

Re: Python 3.x adoption

2014-01-15 Thread Travis Griggs
Here we go again… On Jan 14, 2014, at 11:33 AM, Staszek wrote: > Hi > > What's the problem with Python 3.x? It was first released in 2008, but > web hosting companies still seem to offer Python 2.x rather. > > For example, Google App Engine only offers Python 2.7. > > What's wrong?... Maybe

Re: Python 3.x adoption

2014-01-14 Thread MRAB
On 2014-01-15 02:55, Steven D'Aprano wrote: On Tue, 14 Jan 2014 20:33:50 +0100, Staszek wrote: Hi What's the problem with Python 3.x? Nothing. It was first released in 2008, That was only five years ago. I know that to young kids today who change their iPhone every six months, five year

Re: Python 3.x adoption

2014-01-14 Thread Steven D'Aprano
On Tue, 14 Jan 2014 20:33:50 +0100, Staszek wrote: > Hi > > What's the problem with Python 3.x? Nothing. > It was first released in 2008, That was only five years ago. I know that to young kids today who change their iPhone every six months, five years sounds like a lot, but in the world o

Re: Python 3.x adoption

2014-01-14 Thread Chris Angelico
On Wed, Jan 15, 2014 at 6:33 AM, Staszek wrote: > What's the problem with Python 3.x? It was first released in 2008, but > web hosting companies still seem to offer Python 2.x rather. > > For example, Google App Engine only offers Python 2.7. > > What's wrong?... There's nothing wrong with Python

Re: Python 3.x adoption

2014-01-14 Thread Skip Montanaro
> What's the problem with Python 3.x? It was first released in 2008, but > web hosting companies still seem to offer Python 2.x rather. > > For example, Google App Engine only offers Python 2.7. > > What's wrong?... What makes you think anything's wrong? Major changes to any established piece of s