Hmm, I think I'd give this idea a -0 :-)
Working in an environment where you aren't free to install whatever you want,
because of security concerns, it was very convenient for me to be able to run
Leo as a side effect of the installation of other software that included both
Python 2.7 and PyQt. Only recently has other software which happens to include
Python 3.x and PyQt come on line.
But there are a lot of systems when 2.7 is still the core Python, and adding
"manage multiple Pythons" to the install requirements for Leo adds an
impediment for new users. Ubuntu still uses 2.7 at 16.04 (Long Term Support)
at least, not sure about 16.10 / 17.04, but I wouldn't be surprised if it's
still 2.7.
At the moment I think "packages I can't use in Leo because they're 2.7 only"
would outweigh "packages I can't use in Leo because they're 3.x only", although
I guess that will change.
So, like I said, -0. I think you points about pointing Leo forwards and saving
dev. time are really good, and I guess I'm saying I don't have a strong
opinion... :-}
Cheers -Terry
From: john lunzer <[email protected]>
To: leo-editor <[email protected]>
Sent: Friday, February 10, 2017 12:16 PM
Subject: Re: Warning: imp.reload hurts super and TDD
Edward, doesn't that statement just scream "something is wrong with this" to
you?
Your time is the most precious resource you have. My advice is to do a freeze
of Leo (and it's documentation) at version 5.5 or 5.6 as the last Python 2
compatible version. Make this version available indefinitely. This way people
can get most of the idea of what Leo is about and if they want to "make the
jump" they can go from there. This is no different than what Python itself did.
People got over it eventually. I see people on the forums still using Leo 5.2
for goodness sake. Leo's history is so rich that Leo 5.5/5.6 will be relevant
for years.
One of my favorite Python based tools is xonsh. They made a decision to go with
Python 3 early and never looked back. Nobody rolls up on the forums/git-issues
demanding Python 2 compatibility. Anyone who knows enough to want to demand
Python 2 compatibility knows better than to actually troll a project demanding
such.
Additionally, you may be able to migrate to a Python 3 only codebase and still
support Python 2. Almar Klein, was able to accomplish this with a custom
translator he wrote a blog post about.
http://www.almarklein.org/legacy_python.html
Honestly, give some thought to how much time you will save and how much you can
simplify the code base by going to a Python 3 only implementation of Python.
This could be as important a turning point for Leo as any, and would certainly
align Leo in a completely forward facing direction, which I know is where you'd
like to take Leo.
On Thursday, February 9, 2017 at 2:29:35 PM UTC-5, Edward K. Ream wrote:
On Thu, Feb 9, 2017 at 9:39 AM, 'Terry Brown' via leo-editor
<[email protected]> wrote:
Ha, snap - I just ran into the the same issue with VR-4.
This is one of the best adverts for Python 3 that I know. Alas, we are stuck,
for now, with Python 2.
Funny how nobody complains that pyzo is Python 3 only.
If people only knew how much time I spent futzing with 2/3 issues...
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.
--
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.
