date:20200328

Edward, 

Commit 77f4000d re-adds MANIFEST.in to git exports and releases and is the 
fix for #1547 and #1512, the inability for pip install to work from zip 
release archives. It's worthy of a new dot release. I committed to devel 
before remembering there's a new release branch workflow.

Should I commit this straight to v6.2 branch or create a new v6.2.1 branch 
from v6.2 and then commit? (or something else)

-matt

-- 
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/fa428593-493f-4c2e-9246-ab96b4234225%40googlegroups.com.

Re: Proposed change to setup.py


>
> So if I had a clone at d:\leo-clone, I'd use the following?
>
> python -m pip install --editable d:\leo-clone
>
 
Yes.

I  have been setting PYTHONPATH to d:\leo-clone.  This has always seemed to 
> work well, as long as the dependencies have been installed in my main 
> Python install (because of a previous Leo install, for example).  This way, 
> I can always switch back to using the previous install just by launching 
> from another terminal without setting PYTHONPATH.
>

If your diferent versions are in the same SCM repo (eg. hg, git) then 
resettng to or checking out your desired version can be done without 
messing with PYTHONPATH. This is the primary benefit of editable install, 
it always uses what's in that directory tree *right now, *allowing you to 
test code changes immediately.

pip install -e d:\leo-clone
pushd d:\leo-clone
git checkout v6.1
python -m leo.core.runLeo
# hack, hack. do stuff in Leo 6.1. exit.
git checkout v6.2
python -m leo.core.runLeo
# hack, hack. do stuff in Leo 6.2. exit.
...etc


If you want to run different versions of Leo side by side then *don't *pip 
install Leo at all, editable or not, and set PYTHONPATH the way you have 
been. I think it's cleaner to not to change PYTHONPATH though and to use 
`python d:\leo-clone-2\launchLeo.py` for starting. (It might mess with some 
imports or make them unpredictable as they search in Leo's tree instead of 
the real python tree.)

Also for sde-byside it's best not to use the same HOME, as files in the 
.leo folder might get messed up. 

-matt

-- 
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/b382c3f8-7554-4e21-be6e-106bb165d1f5%40googlegroups.com.

Re: New installation log


>
> I uninstalled Anaconda3. No more confusing envs. Bye bye activation woes.
>

For the benefit of the thread, not because I'm trying to persuade you or 
anyone else to go back to Anaconda or Miniconda:

If you install Leo (or whatever) into the base environment instead of 
creating a distinct envs for projects you can get the simplicity of a 
single system environment, similar to installing python the regular way, 
and still use the conda package manager (if that's a desirable thing for 
your work).

In this case add the base env bin to PATH so it's always available or use 
the system menu 'Anaconda Prompt' (which is the same as `activate` with no 
env specified).

It should be noted this goes against the grain of Anaconda's design and 
they recommend against it. Still works though!

-matt

-- 
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/3701ef09-61ee-4596-b648-6003af1d2e69%40googlegroups.com.

Re: Viewrendered3 Read For Beta Testing

2020-03-28 Thread lewis

I do have nbformat installed.
Since build eb6f4ec070 I get this in console log:
--
Empty setting name in False
set parent @settings
Leo 6.3-devel, devel branch, build eb6f4ec070
2020-03-28 18:58:09 -0500
VR3: *** No Markdown ***
VR3: *** No nbformat
[snip]

However I do not get that message in Leo's log pane. Why are there extra 
messages in the console log about Markdown and nbformat?

Regards
Lewis

-- 
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/c96031c3-5d4a-4527-a260-5b8a908d22cd%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

Hello Matt,

Am Sa., 28. März 2020 um 22:08 Uhr schrieb Matt Wilkie :

> Let's try that again:
> https://leoeditor.com/FAQ.html#how-can-i-arrange-qt-docks
>
> On Saturday, 28 March 2020 14:08:27 UTC-7, Matt Wilkie wrote:
>>
>> Viktor,
>>
>> Thomas Passin contributed his recipe to the FAQ which mightbe helpful:
>>
>
Thanks a lot. - I'll try the recipe tomorrow ...

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/CAAeSrG%2Bpq-nNNQYRmvpP4W7DFpnHrbODmnMcnBdf_QK37xNaog%40mail.gmail.com.

Re: Proposed change to setup.py

On Saturday, March 28, 2020 at 4:45:01 PM UTC-4, Matt Wilkie wrote:
>
>
> I've always installed Leo using pip.  I still don't understand what 
>> "--editable" accomplishes, so I've never used it.
>>
>
> *Pip install* puts the package and all the files it says it needs under 
> PYTHONHOME/Lib/site-packages and creates a launch wrapper in 
> PYTHONHOME/Scripts.
>
> Pip install *--editable* doesn't copy anything, puts link files in Lib 
> pointing to the code location, and creates the launch wrapper to code 
> location. 
>

So if I had a clone at d:\leo-clone, I'd use the following?

python -m pip install --editable d:\leo-clone

I  have been setting PYTHONPATH to d:\leo-clone.  This has always seemed to 
work well, as long as the dependencies have been installed in my main 
Python install (because of a previous Leo install, for example).  This way, 
I can always switch back to using the previous install just by launching 
from another terminal without setting PYTHONPATH.

-- 
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/a3d7c458-edc5-4d04-968e-c5d0e131ccf5%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

Let's try that again:
https://leoeditor.com/FAQ.html#how-can-i-arrange-qt-docks

On Saturday, 28 March 2020 14:08:27 UTC-7, Matt Wilkie wrote:
>
> Viktor,
>
> Thomas Passin contributed his recipe to the FAQ which mightbe helpful:
>
> -matt
>

-- 
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/dd3b522c-e99c-45e2-a25a-c2c3a2a9afd4%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

Viktor,

Thomas Passin contributed his recipe to the FAQ which mightbe helpful:

-matt

-- 
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/15061490-e527-4407-917c-aab082db86b1%40googlegroups.com.

Re: Profiling tree.full_redraw



> g.toUnicodeFileEncoding was called 2504395 times during the exection of my 
> script?! os.path.normpath was called 1128328 times.
>

Wow, that's just crazy. A consequences of our computers being *so* much 
faster than antecedants, like say the Apollo11 lander. We don't feel the 
impact of those millions of extra checks without looking for them.
 

> Once again it turned out that the first step in any optimization effort 
> must be profiling the code. 
>

Thanks. You've renewed my aspiration to learn how to profile. ;-)
 

> I would never guess that the full_redraw used to make so many calls in to 
> the path handling and file system functions.
>

I have a program at work that on startup looks at every file in every 
folder in PATH to see if it matches "filenamexx.dll". Drives me nuts that I 
can't do anything about it.

...icons folder, checking every time for the existence of file icons.
>

One of my back-of-brain ideas is to move all of the icons into a single 
font or svg library file per theme and then use them by name or index 
number. I think it would impove performance, but the initial driver is just 
to remove the thousands "adding file ..." and "copying file ..." messages 
when installing!

-matt

-- 
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/0b834aa4-821e-4c4f-8780-c848a090f644%40googlegroups.com.

Re: Partially solved: installing holoviews

I have updated this Leo file to add Seaborn plots, and to make a few minor 
adjustments in the other examples.  Note that Seaborn uses matplotlib 
behind the scenes.

On Saturday, March 28, 2020 at 12:02:15 AM UTC-4, Thomas Passin wrote:
>
> Here is a Leo outline containing
>
> 1 - Holoview examples using Bokeh, with and without using VR3;
> 2 - Holoviews examples using matplotlib with and without using VR3;
> 3 - Bokeh examples with and without using VR3.
>
> All of these work on my Windows machine as of tonight.  I cleaned them up, 
> corrected for what seem to have been updates to Bokeh (or maybe my 
> misunderstanding), so they are, I think, minimal examples that illustrate 
> how to write the code.  Edward, would you try them out and see what happens 
> with your setup?
>
> Tom
>
> On Friday, March 27, 2020 at 10:09:39 PM UTC-4, Thomas Passin wrote:
>>
>> On Friday, March 27, 2020 at 7:44:33 PM UTC-4, Edward K. Ream wrote:
>>>
>>>
 RuntimeError: Neither firefox and geckodriver nor a variant of chromium 
 browser and chromedriver are available on system PATH. You can install the 
 former with 'conda install -c conda-forge firefox geckodriver'.


>>> I got the same error. I also installed selenium.
>>>
>>
>> Selenium would only be needed for generating a bitmap image.  So I'd say 
>> to stick with my revised code and just use the interactive HTML graphs. 
>>
>

-- 
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/e74f3f5c-cc3e-45b8-a82e-3fc120e49362%40googlegroups.com.


hv_bokeh_examples.leo
Description: Binary data

Re: Proposed change to setup.py



> I've always installed Leo using pip.  I still don't understand what 
> "--editable" accomplishes, so I've never used it.
>

*Pip install* puts the package and all the files it says it needs under 
PYTHONHOME/Lib/site-packages and creates a launch wrapper in 
PYTHONHOME/Scripts.

Pip install *--editable* doesn't copy anything, puts link files in Lib 
pointing to the code location, and creates the launch wrapper to code 
location.  

At present editable is the most reliable because it's guaranteed all files 
are present. The first way leaves some files out. Some are unavoidable 
without deep restructuring of Leo's code repo [#603 
, #573 
] 
and others I'm slowly tracking down and fixing as the bug reports come in 
(and I figure out how to remedy). [#1512 
 and probably #1547 
] 


I recall reading that launchLeo acts different somehow than leo.core.runLeo, 
> but I don't remember the differences. For what it's worth, I normally start 
> Leo with python -m leo.core.runLeo
>

These two methods should be identical. I'm interested in more info if this 
isn't the case.

 -matt

-- 
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/dd289e1c-c036-4ba4-a78d-033cfe611f93%40googlegroups.com.

Re: Proposed change to setup.py



> Anyway, I expanded the docstring of setup.py and put in a guard to prevent 
>> anyone from using it naively like I did.   I've attached below.
>>
>
> Looks good to me. Matt, any comments?
>

Thank you tfer. In all this time it never occured to me to add a message to 
guide people to usng pip instead! I'll use your code with some modification 
to do that. (We have at least one project downstream that uses Leo's 
setup.py directly so we should be mindful not to block that.)

I created #1547  for 
this.

-matt


-- 
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/def3279e-8b88-4104-8a6c-7c0c0bf6c681%40googlegroups.com.

Re: New installation log

Hello Thomas,

Am Sa., 28. März 2020 um 17:12 Uhr schrieb Thomas Passin <
tbp100...@gmail.com>:

> Linux Mint is still on Python 3.6.9.  I think that's what Debian is at
> too, since the Mint package is basically the Debian one, though I'm not
> 100% sure.   Ubuntu is up to 3.7.6
>

I did a quick check for Debian. - The Python 3 version for Debian 10 is
3.7.3

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/CAAeSrGLyed7H0_C6D79y2MWdjucxN_C5Jufv68udue7gu-qC8Q%40mail.gmail.com.

Re: New installation log

Linux Mint is still on Python 3.6.9.  I think that's what Debian is at too, 
since the Mint package is basically the Debian one, though I'm not 100% 
sure.   Ubuntu is up to 3.7.6

On Saturday, March 28, 2020 at 10:00:14 AM UTC-4, Edward K. Ream wrote:

>
> Leo is supposed to run on python 3.6, but python 3.7 looks like the 
> practical minimum for new python installations.
>

-- 
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/5f751f5d-6f9f-4627-bfbe-9282463687f2%40googlegroups.com.

Re: 6.2 final released. Public announcements later

False alarm.  I did successfully upgrade to Leo 6.2 Final via pip on 
Windows.  But I inadvertently fired up Leo from the Github devel branch 
when I went to check the version.  That branch has now moved into the 6.3 
line.  Mea culpa.

On Saturday, March 28, 2020 at 8:12:06 AM UTC-4, Thomas Passin wrote:
>
> I got 6.2 final on Linux too, but not on Windows.
>
> On Saturday, March 28, 2020 at 7:59:09 AM UTC-4, Viktor Ransmayr wrote:
>>
>> Hello Thomas,
>>
>> Am Sa., 28. März 2020 um 12:37 Uhr schrieb Thomas Passin <
>> tbp1...@gmail.com>:
>>
>>> Wait, I just upgraded om Windows using pip with install --upgrade 
>>> leo==6.2, but here's what actually got installed:
>>>
>>> Leo 6.3-devel, VR3 branch, build 22239f2c7b
>>>
>>
>> I did simple a pip install leo --upgrade' - and - the 'startup log is 
>> reporting "Leo 6.2 final".
>>
>> 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/0c510bef-7112-4b92-bbcd-dd270b1210d6%40googlegroups.com.

Thomas, you should have a zoom invite now

Hope to see you soon.

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/702275e9-e92d-46ed-bc83-0bfe7af450a9%40googlegroups.com.

Re: New installation log

On Saturday, March 28, 2020 at 9:28:34 AM UTC-5, Edward K. Ream wrote:


matplotlib is giving a deprecation warning:
>

Rev 35ad24f in devel hacks vr3 to ignore *all* warnings for now.

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/9b2e5653-0fb6-444b-b7ad-28dd8fc73116%40googlegroups.com.

Re: New installation log

On Sat, Mar 28, 2020 at 9:00 AM Edward K. Ream  wrote:

> I'll now experiment with installing the prerequisites for jupyter,
holoviews etc. This should be straightforward with pip.

Indeed it was. Everything is easy with pip. From my notes, not my memory:

*Install nbformat*

Starting Leo message gave this message: `import-jupyter-notebook requires
nbformat package`

> pip install nbformat

Successfully installed
  attrs-19.3.0'
  decorator-4.4.2
  importlib-metadata-1.6.0'
  ipython-genutils-0.2.0
  jsonschema-3.2.0
  jupyter-core-4.6.3
  nbformat-5.0.4
  pyrsistent-0.16.0
  pywin32-227
  six-1.14.0
  traitlets-4.3.3
  zipp-3.1.0

*Install holoviews*

This page  gives various ways of
installing holoviews with pip.

1. The complete installation failed: pip install "holoviews[all]"

ERROR: Could not find a version that satisfies the requirement bzip2; extra
== "all" (from holoviews[all])
   (from versions: none)
ERROR: No matching distribution found for bzip2; extra == "all" (from
holoviews[all])

2. The recommended installation worked: pip install "holoviews[recommended]"

The end of the console log was:

installing collected packages: param, pytz, numpy, python-dateutil, pandas,
pyviz-comms, tqdm, typing-extensions, tornado, MarkupSafe, jinja2, pillow,
PyYAML, pyparsing, packaging, bokeh, markdown, pyct, panel, cycler,
kiwisolver, matplotlib, parso, jedi, pickleshare, pygments, wcwidth,
prompt-toolkit, backcall, colorama, ipython, pyzmq, jupyter-client,
ipykernel, prometheus-client, Send2Trash, testpath, mistune, pandocfilters,
webencodings, bleach, defusedxml, entrypoints, nbconvert, pywinpty,
terminado, notebook, holoviews
Running setup.py install for backcall ... done
Running setup.py install for prometheus-client ... done
Running setup.py install for pandocfilters ... done
Successfully installed
  MarkupSafe-1.1.1
  PyYAML-5.3.1
  Send2Trash-1.5.0
  backcall-0.1.0
  bleach-3.1.4
  bokeh-2.0.0
  colorama-0.4.3
  cycler-0.10.0
  defusedxml-0.6.0
  entrypoints-0.3
  holoviews-1.13.1
  ipykernel-5.2.0
  ipython-7.13.0
  jedi-0.16.0
  jinja2-2.11.1
  jupyter-client-6.1.2
  kiwisolver-1.1.0
  markdown-3.2.1
  matplotlib-3.2.1
  mistune-0.8.4
  nbconvert-5.6.1
  notebook-6.0.3
  numpy-1.18.2
  packaging-20.3
  pandas-1.0.3
  pandocfilters-1.4.2
  panel-0.9.3
  param-1.9.3
  parso-0.6.2
  pickleshare-0.7.5
  pillow-7.0.0
  prometheus-client-0.7.1
  prompt-toolkit-3.0.5
  pyct-0.4.6
  pygments-2.6.1
  pyparsing-2.4.6
  python-dateutil-2.8.1
  pytz-2019.3
  pyviz-comms-0.7.4
  pywinpty-0.5.7
  pyzmq-19.0.0
  terminado-0.8.3
  testpath-0.4.4
  tornado-6.0.4
  tqdm-4.43.0
  typing-extensions-3.7.4.1
  wcwidth-0.1.9
  webencodings-0.5.1

*Install docutils*

Restarting Leo gave this message: Warning: viewrendered3.py running without
docutils.

>pip install docutils

Successfully installed docutils-0.16

*Running holoviews*

At last this script ran within Leo:

import holoviews as hv
hv.extension('matplotlib')
xs = range(-10, 11)
ys = [100-z**2 for z in xs]
curve = hv.Curve((xs, ys))
hv.save(curve, 'curve.png')
print('done')

matplotlib is giving a deprecation warning:

...\Python\Python37\lib\_collections_abc.py:841:
MatplotlibDeprecationWarning:
The datapath rcparam was deprecated in Matplotlib 3.2.1 and will be removed
two minor releases later.

Programs can call warnings.filterwarnings to suppress such things, so it
looks like we are good to go.

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/CAMF8tS3a68cjroiq00fff3WGxP9J3K7p3TD%3DMdvnNeSrHjY3bg%40mail.gmail.com.

Re: 6.2 final released. Public announcements later

Hello Thomas,

Am Sa., 28. März 2020 um 14:23 Uhr schrieb Thomas Passin <
tbp100...@gmail.com>:

> Did you use --upgrade leo==6.2 or just --upgrade leo?
>
> On Saturday, March 28, 2020 at 9:11:27 AM UTC-4, Viktor Ransmayr wrote:
>>
>> Hello Thomas,
>>
>> Am Sa., 28. März 2020 um 13:12 Uhr schrieb Thomas Passin <
>> tbp1...@gmail.com>:
>>
>>> I got 6.2 final on Linux too, but not on Windows.
>>>
>>
>> I got '6.2 final' both on Linux *and* on Windows. The only difference was:
>>
>> * Fedora 30 Linux: An upgrade of an existing PyVE from '6.1-final' to
>> '6.2 final'
>> * Windows 10 Pro: A fresh install into a new PyVE
>>
>
The command for Fedora 30 was "pip install leo --upgrade".

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/CAAeSrGLNCDQczGdx9_rij297u2HBs8%2BqxO%3DMEbRZ_ZRQvqRePw%40mail.gmail.com.

New installation log

I've lost patience with Anaconda3. This thread documents a clean install of
*python
*on Windows. I continue to use Leo's git code.

Imo, virtual environments are a pain in the butt. I've got enough trouble
remembering what git branch I am on. Having multiple forks/envs is too much
for my brain.

Happily, installing python is really simple w/o Anaconda:

*Download*

Python's download page does not seem to
have an executable installer for Python 3.6.x! Clicking 3.6 takes you here
. There are security
problems with 3.6.8, so we really want 3.6.10, but the page only shows two
zipped tarballs. So while Leo is supposed to run on python 3.6, it looks
like we may as well move to 3.7.6.

*Install*

I installed Python 3.7.6 to ~/python/python37, because I dislike installing
anything to "program files". (The space in the name causes problems.) I
checked the "Add python to the path" checkbox. I installed everything
except the python test files.

Attempting to run leo *correctly* raises a Tk dialog saying that Qt can not
be imported.

I upgraded to the latest version of pip, then did `pip install PyQt5`. Now
Leo ran.

*Summary*

I uninstalled Anaconda3. No more confusing envs. Bye bye activation woes.

In the worst case I would would have to reinstall python and all libs. That
would be better than the endless confusion of multiple envs.

It's easy to install python using an executable installer and `pip install
PyQt5`.

Leo is supposed to run on python 3.6, but python 3.7 looks like the
practical minimum for new python installations.

I'll now experiment with installing the prerequisites for jupyter,
holoviews etc. This should be straightforward with pip.

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/856fbc79-74db-4653-8d96-978971d4aee0%40googlegroups.com.

Re: Partially solved: installing holoviews

On Sat, Mar 28, 2020 at 6:57 AM Thomas Passin  wrote:

> I think I see the answer.  When you change something in a Leo node, you do
> not induce Python to re-compile any .pyc files in the various pycaches.
>

Updating a lib might invalidate cached calls *to* the lib if the lib's api
changed.

> If Leo had already loaded matplotlib earlier, then it would reuse that
> compiled code when you did another matplotlib import from within Leo (e.g.,
> when trying out those examples).
>

Updating a lib had better invalidate the lib's caches. Otherwise python is
broken.

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/CAMF8tS3Bcpcsk6U2eJEObA1hTk86B2bfpmJoxkZqW6CwFsQu%3Dg%40mail.gmail.com.

Re: 6.2 final released. Public announcements later

Did you use --upgrade leo==6.2 or just --upgrade leo?

On Saturday, March 28, 2020 at 9:11:27 AM UTC-4, Viktor Ransmayr wrote:
>
> Hello Thomas,
>
> Am Sa., 28. März 2020 um 13:12 Uhr schrieb Thomas Passin <
> tbp1...@gmail.com >:
>
>> I got 6.2 final on Linux too, but not on Windows.
>>
>
> I got '6.2 final' both on Linux *and* on Windows. The only difference was:
>
> * Fedora 30 Linux: An upgrade of an existing PyVE from '6.1-final' to '6.2 
> final'
> * Windows 10 Pro: A fresh install into a new PyVE
>
> 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/8edea38b-31e3-48d8-b2d5-1c7cf7b6d5b2%40googlegroups.com.

Re: 6.2 final released. Public announcements later

Hello Thomas,

Am Sa., 28. März 2020 um 13:12 Uhr schrieb Thomas Passin <
tbp100...@gmail.com>:

> I got 6.2 final on Linux too, but not on Windows.
>

I got '6.2 final' both on Linux *and* on Windows. The only difference was:

* Fedora 30 Linux: An upgrade of an existing PyVE from '6.1-final' to '6.2
final'
* Windows 10 Pro: A fresh install into a new PyVE

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/CAAeSrGLLKCAZXewgXA%2Btw8m0Vb%2BaSCXZzY1JWRWpmq2PPo%3Dngw%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

Hello Edward,

Am Sa., 28. März 2020 um 12:20 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Sat, Mar 28, 2020 at 6:12 AM Viktor Ransmayr wrote:
>
> > Thanks, that helped. - However the panes are now organized in a way,
> that does not feel right (to me).
>
> > That is, the 'Render' pane is to the left of the 'Body' pane - and -
> directly below the 'Outline' pane.
>
> The default for @string initial-split-orientation is now horizontal.
> Change it to vertical.
>

I did try it on Windows - as well as - on Fedora Linux - and - it does not
work as expected :-(

That is the 'Body' pane is at the bottom line of the  4 squares - but - as
I stated in my previous reply, it stays at the *right* bottom square - and
- I'd like to have it at the *left* bottom square ...

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/CAAeSrGLg-1JtucmJGeFe1v%3DBXAfxBoNmJTEnOtoT%3DHxQiMQ%3Diw%40mail.gmail.com.

Re: 6.2 final released. Public announcements later

I got 6.2 final on Linux too, but not on Windows.

On Saturday, March 28, 2020 at 7:59:09 AM UTC-4, Viktor Ransmayr wrote:
>
> Hello Thomas,
>
> Am Sa., 28. März 2020 um 12:37 Uhr schrieb Thomas Passin <
> tbp1...@gmail.com >:
>
>> Wait, I just upgraded om Windows using pip with install --upgrade 
>> leo==6.2, but here's what actually got installed:
>>
>> Leo 6.3-devel, VR3 branch, build 22239f2c7b
>>
>
> I did simple a pip install leo --upgrade' - and - the 'startup log is 
> reporting "Leo 6.2 final".
>
> 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/f282cc8e-2a85-4451-8495-7084a6515522%40googlegroups.com.

Re: 6.2 final released. Public announcements later

Hello Thomas,

Am Sa., 28. März 2020 um 12:37 Uhr schrieb Thomas Passin <
tbp100...@gmail.com>:

> Wait, I just upgraded om Windows using pip with install --upgrade leo==6.2,
> but here's what actually got installed:
>
> Leo 6.3-devel, VR3 branch, build 22239f2c7b
>

I did simple a pip install leo --upgrade' - and - the 'startup log is
reporting "Leo 6.2 final".

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/CAAeSrG%2B9GQXzo04phND%2BAKiXMugunzua06PGLgiE4qFoTxWqhw%40mail.gmail.com.

Re: Partially solved: installing holoviews

I think I see the answer.  When you change something in a Leo node, you do 
not induce Python to re-compile any .pyc files in the various pycaches. If 
Leo had already loaded matplotlib earlier, then it would reuse that 
compiled code when you did another matplotlib import from within Leo (e.g., 
when trying out those examples).   So if something changed in, say, a new 
updated matplotlib package, you wouldn't see it until you deleted all the 
pycache files - or until you ran from a terminal instead of Leo. 

Not exactly a Python bug, then, but say an unexpected feature?

On Saturday, March 28, 2020 at 7:26:58 AM UTC-4, Thomas Passin wrote:
>
> If you want to see something else really strange, the same 
> matplotlib-without-VR3 example that runs successfully with CTRL-B fails to 
> run from a (non-Leo) terminal.  The error says that this line invokes 
> parameters that don't exist.  I had to remove the line and then the plot 
> was produced:
>
> curve1.opts(height=350, width=300)
>
> [Later] After I upgraded Leo from Pypi, the same example no longer runs 
> within Leo until I remove that same line.  I don't see how any caching of a 
> package could survive across multiple restarts of Python, but how else 
> could this be explained?  I wonder if there is a problem with the 
> (relatively) new mechanism that Python uses for deciding whether to 
> re-compile .pyc files in the pycache directories.
>
> I also wonder if this weirdness has something to do with the difference 
> between my results and yours.
>
>
>

-- 
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/5f8fca37-991a-4fbe-a048-ba18cfb13cfd%40googlegroups.com.

Re: 6.2 final released. Public announcements later

Wait, I just upgraded om Windows using pip with install --upgrade leo==6.2, 
but here's what actually got installed:

Leo 6.3-devel, VR3 branch, build 22239f2c7b

On Saturday, March 28, 2020 at 3:39:30 AM UTC-4, Viktor Ransmayr wrote:
>
> Hello Edward, hello Matt,
>
> Am Freitag, 27. März 2020 11:28:24 UTC+1 schrieb Edward K. Ream:
>>
>> Leo 6.2 final is now available here 
>> . Thanks to 
>> all who have contributed.
>>
>> I am going to delay most public announcements until Leo's PyPi package is 
>> available. There is no rush now that the 6.2 branch is separate from devel.
>>
>
> An upgrade of Leo 6.1 to 6.2 using pip & PyPI on Fedora 30 worked like a 
> charm. - Thanks a lot!
>
> 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/70141ce4-df12-461b-afdc-f3ed52912203%40googlegroups.com.

Re: Partially solved: installing holoviews

If you want to see something else really strange, the same 
matplotlib-without-VR3 example that runs successfully with CTRL-B fails to 
run from a (non-Leo) terminal.  The error says that this line invokes 
parameters that don't exist.  I had to remove the line and then the plot 
was produced:

curve1.opts(height=350, width=350)

On Saturday, March 28, 2020 at 4:45:07 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Fri, Mar 27, 2020 at 11:02 PM Thomas Passin  > wrote:
>
>> Here is a Leo outline containing
>>
>> 1 - Holoview examples using Bokeh, with and without using VR3;
>> 2 - Holoviews examples using matplotlib with and without using VR3;
>> 3 - Bokeh examples with and without using VR3.
>>
>> All of these work on my Windows machine as of tonight.  I cleaned them 
>> up, corrected for what seem to have been updates to Bokeh (or maybe my 
>> misunderstanding), so they are, I think, minimal examples that illustrate 
>> how to write the code.  Edward, would you try them out and see what happens 
>> with your setup?
>>
>
> Thanks for this. Very helpful.
>
> I'm seeing something strange. I have a conda holo37 env from which I can 
> import holoviews and matplotlib from the python interp itself.  But the 
> same imports fail when executed from hv_bokeh_examples.leo.
>
> Let me do some researches of various kinds before setting up a zoom 
> meeting.
>
> 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/6b7191af-0358-4eb2-9f28-c9f479c1af7a%40googlegroups.com.

Re: Partially solved: installing holoviews

On Sat, Mar 28, 2020 at 6:15 AM Thomas Passin  wrote:

> That is strange.  Oh, I forgot to write that I ran the non-VR3 examples
> using CTRL-B.  I imagine that's how you tried them, too.
>

Yes, iirc.

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/CAMF8tS15h-jT7Cq84qp3iSJY%3DkucZ9rK4E%2BjVDTtcedmJn4M4A%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

On Sat, Mar 28, 2020 at 6:12 AM Viktor Ransmayr wrote:

> Thanks, that helped. - However the panes are now organized in a way, that
does not feel right (to me).

> That is, the 'Render' pane is to the left of the 'Body' pane - and -
directly below the 'Outline' pane.

The default for @string initial-split-orientation is now horizontal. Change
it to vertical.

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/CAMF8tS16-yj9aaQR31LCsOPQPEP_4jjZ7ALTJurmQT-AnBJBSw%40mail.gmail.com.

Re: Partially solved: installing holoviews

That is strange.  Oh, I forgot to write that I ran the non-VR3 examples 
using CTRL-B.  I imagine that's how you tried them, too.

On Saturday, March 28, 2020 at 4:45:07 AM UTC-4, Edward K. Ream wrote:
>
> On Fri, Mar 27, 2020 at 11:02 PM Thomas Passin  > wrote:
>
>> Here is a Leo outline containing
>>
>> 1 - Holoview examples using Bokeh, with and without using VR3;
>> 2 - Holoviews examples using matplotlib with and without using VR3;
>> 3 - Bokeh examples with and without using VR3.
>>
>> All of these work on my Windows machine as of tonight.  I cleaned them 
>> up, corrected for what seem to have been updates to Bokeh (or maybe my 
>> misunderstanding), so they are, I think, minimal examples that illustrate 
>> how to write the code.  Edward, would you try them out and see what happens 
>> with your setup?
>>
>
> Thanks for this. Very helpful.
>
> I'm seeing something strange. I have a conda holo37 env from which I can 
> import holoviews and matplotlib from the python interp itself.  But the 
> same imports fail when executed from hv_bokeh_examples.leo.
>
> Let me do some researches of various kinds before setting up a zoom 
> meeting.
>
> 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/c6696baf-3209-49ea-a4c7-10ee0146bbe6%40googlegroups.com.

Re: Partially solved: installing holoviews


On Saturday, March 28, 2020 at 4:47:31 AM UTC-4, Edward K. Ream wrote:
>
> On Fri, Mar 27, 2020 at 9:06 PM Thomas Passin  > wrote:
>
> How do you want to work it? 
>>
>
> I'll send a zoom invite to tbp1...@gmail.com . You check 
> that regularly, right?
>
 
Not usually, but I will for the next few days anyway, until I hear from 
you..  The email account I normally use is not a gmail account at all.

As I said in another reply, I'd like to do some homework before setting 
> this up. It might be a day or so.
>

OK. 

-- 
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/b4ffaff7-74c6-40e0-9ea7-535a803e5a30%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

Hello Edward,

Am Sa., 28. März 2020 um 09:53 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:

> On Sat, Mar 28, 2020 at 2:58 AM Viktor Ransmayr 
> wrote:
>
> I did a quick search in the documentation as well as in the FAQ to find
>> information, how to change that back to the way panes where organized in
>> 6.1. - No quick success ...
>>
>> Can you tell me, where I should look?
>>
>
> Good question.  leo -h will show you the command-line options. The
> relevant ones are:
>
> --init-docks  put docks in default positions
> --global-docksuse global docks
> --use-docks   use qt dock widgets
>
> I recommend using --use-docks in your scripts that launch Leo.
>

Thanks, that helped. - However the panes are now organized in a way, that
does not feel right (to me).

That is, the 'Render' pane is to the left of the 'Body' pane - and -
directly below the 'Outline' pane.

What do I have to do to organize the panes as follows: 'Outline [1/1]',
'Tabs [1/2]', 'Body [2/1]' & 'Render [2/2]'?

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/CAAeSrGLf1kN%2BYuSO-PUZAEtBMTEe5%2B8K0mJj8RfKKrddwH8AVQ%40mail.gmail.com.

Profiling tree.full_redraw

2020-03-28 Thread vitalije

This morning I wrote a small script to profile full_redraw method. The
script is:
import cProfile
p1 = p.nodeAfterTree()
g.es('starting')
pr = cProfile.Profile()
pr.enable()
c.selectPosition(p1)
for i in range(20):
c.executeMinibufferCommand('demote')
c.executeMinibufferCommand('promote')
pr.disable()
g.es('finished')
pr.dump_stats('/tmp/stat.txt')
pr.print_stats('time')

The node with this script is at the end of my version of LeoPyRef.leo,
followed by three nodes at the root level a, b and c. After fully expanding
the outline, select this node and execute script. In the console you'll get
stats list sorted by time spent in each function.

I was very surprised to see a lot of functions I didn't expect to see like
g.toUnicodeFileEncoding, os.path.normpath, g.os_path_finalize. ...
g.toUnicodeFileEncoding was called 2504395 times during the exection of my
script?! os.path.normpath was called 1128328 times.

Paths certainly haven't changed during the script execution. There might be
10 (20 at most) different icons in the outline, so I would expect to see at
most 10-20 calls to these functions. How is it possible that there were so
many calls. It turned out that declutter_node was computing icon list for
each node. And for each node on each redraw it was calculating all paths to
themes folder, icons folder, checking every time for the existence of file
icons.

The solution was quite simple, one dict to hold the cached declutter data
and the execution time for the script above went from 31.307 s down to
17.116 s.

New code is already in the devel branch. Revision f71fc76c45.

Once again it turned out that the first step in any optimization effort
must be profiling the code. I would never guess that the full_redraw used
to make so many calls in to the path handling and file system functions.

Vitalije

--
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/9bf28eb8-de1d-47f5-8b7b-3915b6e1b6fb%40googlegroups.com.

Re: Partially solved: installing holoviews

On Fri, Mar 27, 2020 at 8:02 AM Thomas Passin  wrote:

I discovered how to use Bokeh in Holoviews without needing that
> geckodriver.  If you write the actual interactive output - instead of a png
> file - you don't even need a renderer.  You can just embed the interactive
> html output directly.
>

Good to know. Thanks.

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/CAMF8tS0PHLab3XSG%2B%2Bs%3DyPyXNMbtiHrEZ4Kxtcfqtjt2wd9OHA%40mail.gmail.com.

Re: 6.2 final released. Public announcements later

On Sat, Mar 28, 2020 at 2:39 AM Viktor Ransmayr 
wrote:

An upgrade of Leo 6.1 to 6.2 using pip & PyPI on Fedora 30 worked like a
> charm. - Thanks a lot!
>

You're welcome. That's good to know.

I'm not sure whether Matt has actually upgraded the PyPI version...

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/CAMF8tS1OU7mTSq%3Dra1v6TkwNFURGHLkYT121c88O%3Ds08iH1_EA%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

On Sat, Mar 28, 2020 at 2:58 AM Viktor Ransmayr 
wrote:

I did a quick search in the documentation as well as in the FAQ to find
> information, how to change that back to the way panes where organized in
> 6.1. - No quick success ...
>
> Can you tell me, where I should look?
>

Good question.  leo -h will show you the command-line options. The relevant
ones are:

--init-docks  put docks in default positions
--global-docksuse global docks
--use-docks   use qt dock widgets

I recommend using --use-docks in your scripts that launch Leo.

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/CAMF8tS0v0X2eaz6X0UTg4giHsni6KLYyFwuS0082up2baMZQYg%40mail.gmail.com.

Re: Partially solved: installing holoviews

On Fri, Mar 27, 2020 at 9:09 PM Thomas Passin  wrote:

Selenium would only be needed for generating a bitmap image.  So I'd say to
> stick with my revised code and just use the interactive HTML graphs.
>

Will do. This clears up one mystery. The static bitmap image is way less
interesting than the interactive graphs.

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/CAMF8tS2znHAdns%2Bc7xQFtnoxZaHM0dcjj--pQf29A2PybCKaFg%40mail.gmail.com.

Re: Partially solved: installing holoviews

On Fri, Mar 27, 2020 at 9:06 PM Thomas Passin  wrote:

How do you want to work it?
>

I'll send a zoom invite to tbp100...@gmail.com. You check that regularly,
right?

As I said in another reply, I'd like to do some homework before setting
this up. It might be a day or so.

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/CAMF8tS3U7ekyf56RPkchfCzTi1iWJA2TfT%2Bf-n%2BRMpgkKUna-w%40mail.gmail.com.

Re: Partially solved: installing holoviews

On Fri, Mar 27, 2020 at 11:02 PM Thomas Passin  wrote:

> Here is a Leo outline containing
>
> 1 - Holoview examples using Bokeh, with and without using VR3;
> 2 - Holoviews examples using matplotlib with and without using VR3;
> 3 - Bokeh examples with and without using VR3.
>
> All of these work on my Windows machine as of tonight.  I cleaned them up,
> corrected for what seem to have been updates to Bokeh (or maybe my
> misunderstanding), so they are, I think, minimal examples that illustrate
> how to write the code.  Edward, would you try them out and see what happens
> with your setup?
>

Thanks for this. Very helpful.

I'm seeing something strange. I have a conda holo37 env from which I can
import holoviews and matplotlib from the python interp itself.  But the
same imports fail when executed from hv_bokeh_examples.leo.

Let me do some researches of various kinds before setting up a zoom meeting.

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/CAMF8tS07NuD5KRYjkT-J130QL96%3DFp312V5c3x%3DQHrgJR_tMMQ%40mail.gmail.com.

Leo's legacy layout is now the default in version 6.2

Hello Edward,

I did a quick search in the documentation as well as in the FAQ to find 
information, how to change that back to the way panes where organized in 
6.1. - No quick success ...

Can you tell me, where I should look?

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/7c469de4-55ae-43cf-8784-9f743f8ce349%40googlegroups.com.

Re: 6.2 final released. Public announcements later