Hello Thomas, Am Sa., 9. Apr. 2022 um 18:03 Uhr schrieb tbp1...@gmail.com < tbp100...@gmail.com>:
> Thanks, @lewis, @viktor, this is very helpful. We have identified the > cause: The pylint command is run using subprocess.Popen and writes output > (stdout) to a pipe. When there is a lot of output, the output pipe fills > up and the source has to wait until it has room again. So the process > never finishes. You can read the pipe, the the read causes Leo to block > until there is more output again. The size of the pipe would be > os-dependent, so one installation could have success and another remain > stalled forever. > > It's a tricky thing to get this working without blocking Leo. > > On Saturday, April 9, 2022 at 11:09:19 AM UTC-4 viktor....@gmail.com > wrote: > >> Hello everyone, >> >> lewis schrieb am Samstag, 9. April 2022 um 06:11:29 UTC+2: >> >>> I tested with a large file - running pylint on leoGlobals.py gives lots >>> of output. >>> >> >> Trying to to the same on a Leo 'devel' instance in a Fedora VM does not >> return any output at all. >> > Thanks for your quick feedback & update. I'll stop applying the latest changes on the development branch until I hear from you or Edward again. With kind regards, Viktor -- 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/CAAeSrGJie9wBGWnR7odqinVR%3DqqELMV3hmucAyA96dkDss1Bhw%40mail.gmail.com.
