Re: Is it time to require Python 3?

On Thu, Feb 21, 2019 at 8:52 AM Josef wrote: > I think this approach, to keep py3 as a separate branch, is a good > compromise. > Thanks for these comments. I think the matter is settled, for now. Edward -- You received this message because you are subscribed to the Google Groups

Re: Is it time to require Python 3?

Hello Edward, I think this approach, to keep py3 as a separate branch, is a good compromise. As far as I can see, the long-term-support versions of Ubuntu and derivatives still run on py2 per default. Installing another python version on top of this is not quite suitable for non-programmers. I

Re: Is it time to require Python 3?

> As I recall (dimly perhaps), that the default spell checker does not work > w/ P3? Don't remember what I did, but spell checking works for me now > (Python v3.4.3). > background library has gone into no-longer-maintained status: https://github.com/leo-editor/leo-editor/issues/1080 -- You

Re: Is it time to require Python 3?

As I recall (dimly perhaps), that the default spell checker does not work w/ P3? Don't remember what I did, but spell checking works for me now (Python v3.4.3). Other than that, it seems like the way to go, especially as P2 will not be supported in the foreseeable future. Rob... -- You

Re: Is it time to require Python 3?

On Tuesday, February 19, 2019 at 8:55:19 AM UTC-6, Edward K. Ream wrote: > ...there are costs associated with removing Python 2 compatibility... As I contemplate diving into Pharo, I see that Leo 5.8.2 might be Leo's last version. Don't panic. I'll continue to work on Leo for as long as I am

Re: Is it time to require Python 3?

On Sunday, February 17, 2019 at 5:56:33 PM UTC-6, Edward K. Ream wrote: > There are real costs associated with retaining Python 2 compatibility, and I am unwilling to bear those costs indefinitely. These costs include increased testing and distribution complexity, and foregoing Python 3

Re: Is it time to require Python 3?

On Tue, Feb 19, 2019 at 5:53 AM john lunzer wrote: I think Matt has a good point, if you're going to jump the Python2 ship you > might as well jump into the latest model. 3.6 seems reasonable, it was > released December 23, 2016. > What version of Python 3 is available on Linux, MacOs and

Re: Is it time to require Python 3?

> > If it won't cause trouble with downstream distributions I'd even go so far >> as to request v3.6+ -- simply because I absolutely love f-string formatting >> ( >> https://www.blog.pythonlibrary.org/2018/03/13/python-3-an-intro-to-f-strings/ >> ). >> > > We can consider that later. > I think

Re: Is it time to require Python 3?

On Monday, February 18, 2019 at 10:01:49 PM UTC-6, Matt Wilkie wrote: > > Matt, what effect will requiring Python 3 have on your work? >> > > All good effects. I've been testing with both so I expect it to be > seamless. I'll be able to remove some testing and if/then parsing. All in > all it

Re: Is it time to require Python 3?

> > Matt, what effect will requiring Python 3 have on your work? > All good effects. I've been testing with both so I expect it to be seamless. I'll be able to remove some testing and if/then parsing. All in all it will be simpler. If it won't cause trouble with downstream distributions I'd

Re: Is it time to require Python 3?

On Mon, Feb 18, 2019 at 4:40 AM Edward K. Ream wrote: > My plan is to make this transition in Leo as soon as Leo 5.8.1 goes out the door. This should happen in a few weeks. Today's work in the py3 branch removes all Python 2 dependencies, that is, all significant tests for g.isPython3. So in

Re: Is it time to require Python 3?

On Monday, February 18, 2019 at 4:22:18 AM UTC-6, Edward K. Ream wrote: Leo has been "slowly jumping into Py3" ever since Python 3.0. I agree with > Vitalije. There are many reasons to prefer Py3. > The Python 2.7 Countdown page indicates that Python 2 will retire

Re: Is it time to require Python 3?

On Sunday, February 17, 2019 at 6:21:03 PM UTC-6, Zoom.Quiet wrote: > > IMHO: > > if Python 2.7 can support all Leo running env. > not big reason had to jump into Py3; > dont panic, slow slowly jump it. > Leo has been "slowly jumping into Py3" ever since Python 3.0. I agree with Vitalije.

Re: Is it time to require Python 3?

On Sunday, February 17, 2019 at 9:28:04 PM UTC-6, Matt Wilkie wrote: Given that Python.org has set the end of life for python v2 to be only 8 > months from now, 2020, I think it's fine to talk about not supporting it > longer in Leo. I suggest doing that in v6 rather than 5.9 though as it >

Re: Is it time to require Python 3?

On Mon, Feb 18, 2019 at 2:34 AM vitalije wrote: This is an excellent idea. Python3 is really much faster than Python2 when > its new features are used. Right now, many of its features can't be used > because of Python2 support. Leo still performs lots of unicode/str > checking/converting just

Re: Is it time to require Python 3?

This is an excellent idea. Python3 is really much faster than Python2 when its new features are used. Right now, many of its features can't be used because of Python2 support. Leo still performs lots of unicode/str checking/converting just because it needs to be compatible with both versions.

Re: Is it time to require Python 3?

Given that Python.org has set the end of life for python v2 to be only 8 months from now, 2020, I think it's fine to talk about not supporting it longer in Leo. I suggest doing that in v6 rather than 5.9 though as it would mark a major break (and it would be fine to skip 5.9). matt -- You

Re: Is it time to require Python 3?

IMHO: if Python 2.7 can support all Leo running env. not big reason had to jump into Py3; dont painc, slow slowly jump it. Edward K. Ream 于2019年2月18日周一 上午7:56写道： > > I've asked this question before. Imo, abandoning Python 2 should happen > eventually, say at Leo 5.9. Those who must use