Re: Why Python 4.0 won't be like Python 3.0

Newsgroups	comp.lang.python
Date	2014-08-18 01:30 -0700
References	<lsq7lg$8tp$2@ger.gmane.org> <D1E2A969-19AB-42C7-A9C3-DF9DA3D6576D@gmail.com> <mailman.13079.1408329145.18130.python-list@python.org>
Message-ID	<99ae1b64-b6cd-42c1-9dba-d98eb710418e@googlegroups.com> (permalink)
Subject	Re: Why Python 4.0 won't be like Python 3.0
From	wxjmfauth@gmail.com

Show all headers | View raw

Le lundi 18 août 2014 04:32:23 UTC+2, Chris Angelico a écrit :
> On Mon, Aug 18, 2014 at 9:17 AM, Redge @ Versalytics.com
> 
> <versalytics@gmail.com> wrote:
> 
> > Definitely a relief. After delving into Python only a few short months ago, everything I was reading suggested 2.x.x. When I switched to another book to continue with my studies, some of the code wasn't working ... welcome to 3.x.x.  Needless to say, I'm using 3.4.1 exclusively today unless something bizarre requires me to do otherwise.
> 
> >
> 
> 
> 
> Good move. You should be able to upgrade to 3.4.x safely, and 3.5 fairly safely.
> 
> 
> 
> Eventually, books about Python 3 will be the more easily found, and
> 
> you won't have this kind of confusion.
> 
> 
> 
> ChrisA

LibreOffice contains a Python 3 scripting engine.
Just for the fun, I take a look with Writer.
It simply fails on a valid string (as I expected).
However, LibreOffice does not crash (or may not crash).
I do no know how these "errors" are intercepted.
Unfortunately, that's not the case in Python GUI wrappers.

jmf

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-18 12:32 +1000
  Re: Why Python 4.0 won't be like Python 3.0 wxjmfauth@gmail.com - 2014-08-18 01:30 -0700

csiph-web