> I am answering my original post. A workaround for me was to grab leo from
> github and run from master. For whatever reason, that version works
> properly. The still installed pip version continues to misbehave, no idea
> what is going on. Since my purpose was simply to have a working ve
I am answering my original post. A workaround for me was to grab leo from
github and run from master. For whatever reason, that version works
properly. The still installed pip version continues to misbehave, no idea
what is going on. Since my purpose was simply to have a working version of
On Fri, Feb 13, 2015 at 2:23 AM, Zoom.Quiet wrote:
> flow Installing Leo — Leo 5.0 documentation
> http://leoeditor.com/installing.html
> re-check all :
>
> $ brew doctor
>
[snip]
>
> so just
>
> $ brew link pyqt
>
> Wow dear Leo come back ;-)
>
> thanx for all.
>
> the off
> i
> cial
flow Installing Leo — Leo 5.0 documentation
http://leoeditor.com/installing.html
re-check all :
$ brew doctor
...
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `br
On Thu, Feb 12, 2015 at 9:45 AM, Zoom.Quiet wrote:
> just today, i can not running Leo5.0-final through old scrip:
>
I suggest asking for help from the Apple brew people, or possibly the PyQt
people. The problems you are having arise from pyqt not being available.
Any other Leo users have any
just today, i can not running Leo5.0-final through old scrip:
$ python /opt/bin/leo/launchLeo.py
leoQt.py: can not import either PyQt4 or PyQt5.
Traceback (most recent call last):
File "/opt/bin/leo/launchLeo.py", line 7, in
import leo.core.runLeo
File "/opt/bin/Leo5.0-final/leo/core/runL
On Wed, Jan 28, 2015 at 6:24 AM, Fidel N wrote:
>
> Perhaps a warning message/GUI should appear to tell the user to check if
> he did install pyqt properly?
>
In future, whenever you have problems installing Leo, or really, any other
program, the first thing to try is to run the program from a
That would be kind of hard without PyQT! I suppose a fallback into
tkinter could be used for this.
-->Jake
On 1/28/2015 7:24 AM, Fidel N wrote:
I also had troubles back in the time when installing, and it also was
because of unproperly / not installed pyqt.
Perhaps a warning message/GUI shoul
I also had troubles back in the time when installing, and it also was
because of unproperly / not installed pyqt.
Perhaps a warning message/GUI should appear to tell the user to check if he
did install pyqt properly?
I think this could be a frequent bummer for new users who just don't spend
more
thanks,
it's funny once you get it up and running (in my case 64 bit with PyQt4)
you just want to go on and use it
rather than figuring out what the issues were that made me stumble on the
installation.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" gr
On Tue, 27 Jan 2015 14:59:36 -0800 (PST)
Todd Mars wrote:
> Trying to install on a new windows system.
> I installed Python34 which goes into C:\Python34
> I installed DocUtils
> PyQt GPL v5.4 for Python v3.4 (x64) Setup reports an error and if I
> install it anyway Leo has an error.
The setup r
I think a very hard issue is setup of the full system. I have now 4
computers and 2 have working versions on them and 2 have non-working
versions.
A simple procedure would be great, that would work on a clean computer
(Windows 7 or 8)
Todd.
On Tuesday, January 27, 2015 at 5:59:37 PM UTC-5, T
Trying to install on a new windows system.
I installed Python34 which goes into C:\Python34
I installed DocUtils
PyQt GPL v5.4 for Python v3.4 (x64) Setup reports an error and if I install
it anyway Leo has an error.
"This copy of PyQt has been built against Python v3.4 (x64) which doesn't
seem t
On Tue, Jan 14, 2014 at 2:55 PM, Terry Brown wrote:
>
>
> Qt5 moves most of QtGui.* to QtWidgets.*, but not all.
Interesting. It shouldn't be too hard to change references in a
version-neutral way. I'll put it on the list of things to play with.
Edward
--
You received this message becaus
On Tue, 14 Jan 2014 14:49:50 -0600
"Edward K. Ream" wrote:
> On Wed, Jan 8, 2014 at 9:29 AM, Viktor Ransmayr
> wrote:
>
> Leo only works with PyQt4. - I had the same problem a while ago. - I tried
> > many variations, but only succeeded with PyQt4 ...
> >
>
> The reason seems clear: Leo's sour
On Wed, Jan 8, 2014 at 9:29 AM, Viktor Ransmayr
wrote:
Leo only works with PyQt4. - I had the same problem a while ago. - I tried
> many variations, but only succeeded with PyQt4 ...
>
The reason seems clear: Leo's sources use import such as::
import PyQt4.QtCore
I never realized how stran
Hello Todd,
Am Mittwoch, 8. Januar 2014 16:14:18 UTC+1 schrieb Todd Mars:
>
> Hi!
> I have a new 64 bit install, I have Python33 and PyQT5. And Leo-4.11-final.
> When I execute Python lauch-leo.py, I get errors PyQt4 no module named,
> ImportErrors, etc.
> So, where's that association?
>
Leo onl
On 1/8/2014 10:14 AM, Todd Mars wrote:
Hi!
I have a new 64 bit install, I have Python33 and PyQT5. And
Leo-4.11-final.
When I execute Python lauch-leo.py, I get errors PyQt4 no module
named, ImportErrors, etc.
So, where's that association?
Thanks
Todd.
You probably need to install PyQT4, not
Hi!
I have a new 64 bit install, I have Python33 and PyQT5. And Leo-4.11-final.
When I execute Python lauch-leo.py, I get errors PyQt4 no module named,
ImportErrors, etc.
So, where's that association?
Thanks
Todd.
--
You received this message because you are subscribed to the Google Groups
"leo
Leo 4.10 final, build 5020, 2012-02-26 13:18:08 -0600
Python 2.7.3, qt version 4.8.1
linux2
So I fresh-installed new OS version and LEO.
Should I just copy over the entire old backed-up .leo folder to the
new Home ?
What is the "db" folder ? Can I skip copying over the "db" folder ?
--
You re
20 matches
Mail list logo