Re: Leo 5.x no longer working in my Windows 10 environment

2016-06-28 Thread Viktor Ransmayr
I used the "PyQt5-5.6-gpl-Py3.5-Qt5.6.0-x64.exe" from https://www.riverbankcomputing.com/software/pyqt/download5 On Wed, Jun 29, 2016 at 12:40 AM, Edward K. Ream wrote: > > > On Tue, Jun 28, 2016 at 4:53 PM, Edward K. Ream > wrote: > >> >> >> On Tue, Jun 28, 2016 at 1:21 PM, Viktor Ransmayr <

Re: Leo 5.x no longer working in my Windows 10 environment

2016-06-28 Thread Edward K. Ream
On Tue, Jun 28, 2016 at 4:53 PM, Edward K. Ream wrote: > > > On Tue, Jun 28, 2016 at 1:21 PM, Viktor Ransmayr < > viktor.ransm...@gmail.com> wrote: > >> Hello Edward, >> >> I would accept that *somehow* one file(-name) changed - but - I'm sure >> you saw that I also started Leo w/o an explicit ou

Re: Leo 5.x no longer working in my Windows 10 environment

2016-06-28 Thread Edward K. Ream
On Tue, Jun 28, 2016 at 1:21 PM, Viktor Ransmayr wrote: > Hello Edward, > > I would accept that *somehow* one file(-name) changed - but - I'm sure you > saw that I also started Leo w/o an explicit outline argument ... > > Please let me know if there is anything else you want me to deliver. - > Ot

Re: Leo 5.x no longer working in my Windows 10 environment

2016-06-28 Thread Viktor Ransmayr
Hello Edward, I would accept that *somehow* one file(-name) changed - but - I'm sure you saw that I also started Leo w/o an explicit outline argument ... Please let me know if there is anything else you want me to deliver. - Otherwise I plan to completely erase this environment ... With kind reg

Re: leo 5.2 can not run in MAC OS X 10.11.5

2016-06-28 Thread Edward K. Ream
On Tue, Jun 28, 2016 at 1:03 AM, Zoom.Quiet wrote: > > In short, Leo is not able to import PyQt4 or PyQt5. > > Yes, sorry for all, > forget under python install PyQt4 > because my pyenv had to reinstall all. > > thanks for all, > leo re-working now. > ​It's no problem. I'm glad things are worki

Re: Leo 5.x no longer working in my Windows 10 environment

2016-06-28 Thread Edward K. Ream
On Tue, Jun 28, 2016 at 12:59 AM, Viktor Ransmayr wrote: > Hello Edward, > > Thanks for your quick feedback! > ​You're welcome.​ > > Here are the new tracebacks, when I call it with an explicit outline > argument > ​[lots of null characters] !!! What irritates me is that something changed *w