Re: Different results of 'test-all' cmd

On Sun, May 22, 2022 at 9:44 AM tbp1...@gmail.com wrote: > > IMO, the most reliable way to locate the Leo directory is this (run on > Linux Mint): > > >>> import os.path, leo > >>> print(os.path.dirname(leo.__file__)) > /home/tom/git/leo-editor/leo > A great suggestion. I use a variant of this

Re: Different results of 'test-all' cmd

On Sun, May 22, 2022 at 9:44 AM tbp1...@gmail.com wrote: > I have noticed that there have been a number of expressions used to try to > find Leo's directory, to try to handle or work around problems like this. > Some of them involve finding the sitepackages directory. I want to point > out that

Re: Different results of 'test-all' cmd

I have noticed that there have been a number of expressions used to try to find Leo's directory, to try to handle or work around problems like this. Some of them involve finding the sitepackages directory. I want to point out that most of these efforts make assumptions that are incorrect for

Re: Different results of 'test-all' cmd

On Sun, May 22, 2022 at 1:50 AM Edward K. Ream wrote: > On Sun, May 22, 2022 at 1:30 AM Viktor Ransmayr > wrote: > > >> In short, there is no feasible way to run Leo's test and cover > commands after `pip install leo`. > >> >> I believe, that this difference b/w **Leo-Editor** from GitHub - and

Re: Different results of 'test-all' cmd

On Sun, May 22, 2022 at 1:30 AM Viktor Ransmayr wrote: >> In short, there is no feasible way to run Leo's test and cover commands after `pip install leo`. > > I believe, that this difference b/w **Leo-Editor** from GitHub - and - > **Leo** from PyPI should be documented. > I agree. The place

Re: Different results of 'test-all' cmd

Hello Edward, Am Sa., 21. Mai 2022 um 13:24 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > On Fri, May 20, 2022 at 3:32 PM Edward K. Ream > wrote: > >> >> 1. I am not going to change Leo's test-all command so that it works in >> python/site-packages/leo. The workaround is easy: run

Re: Different results of 'test-all' cmd

On Fri, May 20, 2022 at 3:32 PM Edward K. Ream wrote: On Sunday, May 1, 2022 at 3:54:07 AM UTC-5 viktor@gmail.com wrote: > > 1. I am not going to change Leo's test-all command so that it works in > python/site-packages/leo. The workaround is easy: run `python -m unittest` > from

Re: Different results of 'test-all' cmd

On Sunday, May 1, 2022 at 3:54:07 AM UTC-5 viktor@gmail.com wrote: Lately I have adapted my defaults a bit - and - execute 'test-all' cmd > whenever I modify / upgrade any Leo instance. > > Doing this now also with versions I downloaded directly from PyPI I > noticed that 'test-all' cmd

Re: Different results of 'test-all' cmd

On Sun, May 1, 2022 at 9:54 AM Viktor Ransmayr wrote: I guess my intro was to short - and/or - completely missing ;-) > > What I noticed is that the two **major** variants of how (many! /most?) > people install Leo nowadays behave differently: > > * Running 'test-all' cmd on a Leo version 6.6*

Re: Different results of 'test-all' cmd

Hello Edward, Edward K. Ream schrieb am Sonntag, 1. Mai 2022 um 15:04:14 UTC+2: > On Sun, May 1, 2022 at 3:54 AM Viktor Ransmayr wrote: > > Lately I have adapted my defaults a bit - and - execute 'test-all' cmd >> whenever I modify / upgrade any Leo instance. >> > > Thanks for your continued

Re: Different results of 'test-all' cmd

On Sun, May 1, 2022 at 8:47 AM tbp1...@gmail.com wrote: > And on my system, pylint still can check freewin without crashing: This might be related to another pylint issue I reported, #6476 . After reporting this bug I realized that there is a simple

Re: Different results of 'test-all' cmd

And on my system, pylint still can check freewin without crashing: Your code has been rated at 9.95/10 (previous run: 9.89/10, +0.05) On Sunday, May 1, 2022 at 9:19:50 AM UTC-4 Edward K. Ream wrote: > On Sunday, May 1, 2022 at 8:04:14 AM UTC-5 Edward K. Ream wrote: > > > I am running pylint

Re: Different results of 'test-all' cmd

On Sunday, May 1, 2022 at 8:04:14 AM UTC-5 Edward K. Ream wrote: > I am running pylint tests as I write this. Some complaints may remain. If necessary I'll create a PR. pylint is happy on python 3.9, but for python 3.10 dozens of messages such as: leo\core\leoBackground.py:122:12: E1120: No

Re: Different results of 'test-all' cmd

On Sunday, May 1, 2022 at 8:04:14 AM UTC-5 Edward K. Ream wrote: > pylint issue #6438 [and] issue #1534 ...involve astroid, a package that handles ast nodes. At present pylint-leo skips

Re: Different results of 'test-all' cmd

On Sun, May 1, 2022 at 3:54 AM Viktor Ransmayr wrote: Lately I have adapted my defaults a bit - and - execute 'test-all' cmd > whenever I modify / upgrade any Leo instance. > Thanks for your continued testing, which is one of the most important tasks in maintenance mode. > Doing this now also

Different results of 'test-all' cmd

Hello Edward, Lately I have adapted my defaults a bit - and - execute 'test-all' cmd whenever I modify / upgrade any Leo instance. Doing this now also with versions I downloaded directly from PyPI I noticed that 'test-all' cmd returns failures & errors. * See "Log-001" for the results of the