Hello Edward, hello Matt, Am Sonntag, 22. September 2019 23:01:41 UTC+2 schrieb Viktor Ransmayr: > > Hello Edward, hello Matt, > > Am Samstag, 13. Juli 2019 17:07:44 UTC+2 schrieb Viktor Ransmayr: >> >> Hello Edward, hello Matt, >> >> ... >> >> Installing Leo-devel via pip from GitHub into a new VE still does not >> work. >> >> ... >> >> Now that Leo 6.1 is coming up, I tried again to use Leo-Dev in a > dedicated Python Virtual Environment (PyVE) downloaded from GitHub & > installed using pip. > > I'm running again into the same - or - a very similar situation. > > As you can see from my worklog, this time the current instance of Leo > (let's call it Leo-stable) was explicitly closed before I started the new > instance of Leo-devel. > > Any idea or recommendation what to try next? >
I'm trying to follow the suggestion from Edward concerning the quality of bug reports/ inquiries. - Therefore let me re-start with a question: *Should it be possible to upgrade Leo in a given Python Virtual Environment from one Git revision to another one using the command "pip install https://github.com/leo-editor/leo-editor/archive/devel.zip --upgrade"?* If you confirm that this is a supported workflow, than I'll invest all the time necessary to resolve this issue ... 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b43cd12f-7313-41d2-a031-00532e641d2b%40googlegroups.com.
