On Tuesday, June 20, 2017 at 10:27:05 AM UTC-5, Kent Tenney wrote: I'm not up on the specifics, but folks seem excited about language > improvements available in [python] 3.6, at some point in time it will make > sense to use those features, resulting in code that won't work on 2.7. >
Oh great. Now we will have a true fork in Python. Imo, this will be a serious self inflicted wound in the Python world. > The tipping point if not now, near. That's what I meant. > I would be happy to support Python 3 only. Almost all my development work starts on Python 3. But what about Leo's users? How am I to demand that they all switch to Python 3? And if I can't do that, how am I going to support two *separate* code bases? The answer is, I won't. So Leo will perforce have to stick with features common to Python 2.7 up to Python 3.5. This will work for awhile, but will become less and less attractive unless bug fixes are back-ported from Python 3.6 to Python 2.7 and 3.5. I doubt that this will happen for long. I have a bad feeling about this. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
