Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: > For more straightforward scripting engine uses, there's always Lua, though > the >> fork of Lua done to implement a JIT trails the main >> implementation . There is an interest

Re: Managing Python 2.7 Code In Leo

> > On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: >> >>> Jython support for Python3 is planned >>> and roadmapped >>> . >>> >> >> Yes, and have you noticed the huge amount of work those

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 5:18:15 PM UTC-5 tbp1...@gmail.com wrote: > On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: > >> Jython support for Python3 is planned >> and roadmapped >>

Re: Managing Python 2.7 Code In Leo

On Mon, Jan 17, 2022 at 9:10 AM tbp1...@gmail.com wrote: > That setting is not among the settings listed in the output of > Settings/Show Settings/Show-Settings. [M] @ bool checkforchangedexternalfiles = True The name shown is the "dictionary" name, with "-" and "_" deleted. In any case, leo

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: > Jython support for Python3 is planned > and roadmapped > . > Yes, and have you noticed the huge amount of work those plans will entail?

Re: Managing Python 2.7 Code In Leo

The Graal system can also run jython or jython-like code to some degree. They added some improved support for inheriting from jython/pythonIntroduction to GraalVM classes in java at my request. See, e.g., Inheritance from Java

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 6:01:43 AM UTC-5 Edward K. Ream wrote: > On Sun, Jan 16, 2022 at 3:08 PM tbp1...@gmail.com > wrote: > >> The project is a Tomcat web application that uses mixed java and Jython. > > > VSCode probably allows you to use python 2 for some projects. I am not > going

Re: Managing Python 2.7 Code In Leo

That setting is not among the settings listed in the output of Settings/Show Settings/Show-Settings. I now, after your post, see that it is included in leoSettings.leo, where I had to try various guesses as to what the setting might be called before finally noticing it. I started searching f

Re: Managing Python 2.7 Code In Leo

On Mon, Jan 17, 2022 at 7:30 AM tbp1...@gmail.com wrote: > Probably being able to disable automatic syntax checking in an outline > would be enough. Is there a setting to do that? > @bool check-python-code-on-write In future, please search for settings before asking about them. Edward -- Yo

Re: Managing Python 2.7 Code In Leo

Probably being able to disable automatic syntax checking in an outline would be enough. Is there a setting to do that? On Monday, January 17, 2022 at 6:01:43 AM UTC-5 Edward K. Ream wrote: > On Sun, Jan 16, 2022 at 3:08 PM tbp1...@gmail.com > wrote: > >> The project is a Tomcat web applicatio

Re: Managing Python 2.7 Code In Leo

On Sun, Jan 16, 2022 at 3:08 PM tbp1...@gmail.com wrote: > The project is a Tomcat web application that uses mixed java and Jython. VSCode probably allows you to use python 2 for some projects. I am not going to support python 2 in Leo, but a plugin could do so. Edward -- You received this m

Re: Managing Python 2.7 Code In Leo

The project is a Tomcat web application that uses mixed java and Jython. Most of the work is done with Jython, but there are some things that need java. In some places, java code calls Jython objects and methods, in other places Jython code calls into java. It works great. I've been supporting

Re: Managing Python 2.7 Code In Leo

Can't do it for at least one case. The code is Jython 2.7, and it will be a long time, if ever, before Jython gets up to 3+. On Sunday, January 16, 2022 at 2:11:08 PM UTC-5 Edward K. Ream wrote: > On Sun, Jan 16, 2022 at 12:20 PM tbp1...@gmail.com > wrote: > >> Now that Leo is Python 3.6+ onl

Re: Managing Python 2.7 Code In Leo

On Sun, Jan 16, 2022 at 12:20 PM tbp1...@gmail.com wrote: > Now that Leo is Python 3.6+ only, there is a question about using it to > maintain old Python 2.x code, of which I have some that can't be converted > to Python 3.6+. The issue, of course, is that checkers like flake8 will > report erro

Managing Python 2.7 Code In Leo

Now that Leo is Python 3.6+ only, there is a question about using it to maintain old Python 2.x code, of which I have some that can't be converted to Python 3.6+. The issue, of course, is that checkers like flake8 will report errors which aren't actual errors for 2.7 code. This is a best a nu