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 and slowly developing this application since about 2007. There is zero chance I would ever convert it to all java, that would be too unpleasant to contemplate (and my client would not want to cover the cost to do it).
On Sunday, January 16, 2022 at 2:37:00 PM UTC-5 tbp1...@gmail.com wrote: > 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 <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 errors which aren't actual errors for 2.7 code. This is a best a >>> nuisance and at worst might lead to failure to save files. >>> >>> What's the best way to handle these older Python files in Leo? >>> >> >> Convert them to python 3.x. >> >> 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/33adba65-bea3-4ee5-ad7b-62dd9a5a1d88n%40googlegroups.com.
