Re: Ville: ok to put setup.py in leo/dist folder?

On Sat, Oct 25, 2014 at 5:25 PM, Kent Tenney wrote: > ? > I've been very pleased for access to setup.py capability: > (venv)ktenney@lappy:leo-editor $ pip install -e . -U If you and Matt use setup.py this way, does this mean that the bug is invalid? Edward -- You received this message because

Re: Houston, we have a problem with gnx's

On Wed, Oct 22, 2014 at 6:35 PM, 'Terry Brown' via leo-editor wrote: > Of course, given the three alternatives to clones Leo has, I /personally/ > would be fine with clone free Leo, but I know they're Leo's killer feature > for a lot of people. Gnx's would be important even without clones: the

Re: Ville: ok to put setup.py in leo/dist folder?

On Sat, Oct 25, 2014 at 3:25 PM, Kent Tenney wrote: > Am I alone in making use of setup.py to install? I use it. It's my preferred method (via pip) when I'm on a computer that already has python and [yqt. -matt -- You received this message because you are subscribed to the Google Groups "l

Re: Ville: ok to put setup.py in leo/dist folder?

? I've been very pleased for access to setup.py capability: (venv)ktenney@lappy:leo-editor $ pip install -e . -U depends on setup.py Am I alone in making use of setup.py to install? On Sat, Oct 25, 2014 at 11:04 AM, Edward K. Ream wrote: > On Sat, Oct 25, 2014 at 8:08 AM, Kent Tenney wrote: >

Re: Ville: ok to put setup.py in leo/dist folder?

On Sat, Oct 25, 2014 at 8:08 AM, Kent Tenney wrote: > My prediction: > For each confused newbie (facing a learning opportunity) there > will be many pythonistas wondering why in the world setup.py > is in the wrong place, do these folks not understand packaging? That would be an argument for keep

Re: Ville: ok to put setup.py in leo/dist folder?

My prediction: For each confused newbie (facing a learning opportunity) there will be many pythonistas wondering why in the world setup.py is in the wrong place, do these folks not understand packaging? On Sat, Oct 25, 2014 at 6:34 AM, Edward K. Ream wrote: > Can you live with setup.py somewher

Re: Houston, we have a problem with gnx's

On Fri, Oct 24, 2014 at 3:00 PM, Todd Mars wrote: > The fact that GNX is considered visually intrusive is a separate issue. No, it's not. gnx's are visible in sentinel comments, and they must be stored internally in exactly the same form. > My diagnosis: you are confusing two diseases as havin

Re: Upgrading to Py34 and QT5, Leo won't load files

On Fri, Oct 24, 2014 at 8:18 PM, Largo84 wrote: > OK, I sort of figured out that pythonw.exe doesn't work, but python.exe (at > least on Python3.3 and any version of QT). > > But now I get this: ... > line 79, in > from PyQt5.QtCore import SIGNAL, QTimer # QSize, QVariant, > ImportError: cann

Ville: ok to put setup.py in leo/dist folder?

Can you live with setup.py somewhere other than the top-level folder? Hiding setup.py seems like the only way to resolve git bug #81 https://github.com/leo-editor/leo-editor/issues/81 Various forms of this issue have been around for years. Edward -- You received this message because you are s

Re: new clone-node-to-last-node command

On Thursday, October 23, 2014 7:07:14 PM UTC-5, Edward K. Ream wrote: Just like the clone-node command except a) it moves the cloned node to the > last *top-level* node and b) it leaves the selected node unchanged. Kind > of a lightweight clone-find-all command: very handy for quickly cloning

Re: Schedule for Leo 5.0a1

On Wednesday, October 22, 2014 11:22:51 AM UTC-5, Edward K. Ream wrote: > > > Guesstimate: a1 will go out the door about Monday, October 27. This > release will not be widely advertized: its primary purpose is to test the > release process itself. > My present plan is to release on Friday, Oc