Re: Mac import error after update

[Rob]

Yes, but I don't know how to upgrade Python on the Mac. Seems like the 
default installation 2.7 or something. I can manage this on my PC, but the 
Mac is a complete mystery to me how to do that. (Wish I didn't have to deal 
with it, but it's my travel laptop and am only marginally proficient at it, 
especially with command line stuff.)

Rob...

On Thursday, July 25, 2019 at 1:06:16 PM UTC-4, Edward K. Ream wrote:
>
>
>
> On Thu, Jul 25, 2019 at 6:31 AM Rob > 
> wrote:
>
>> Since the last big Leo upgrade in June, I can't get it to start on macOS 
>> Mojave (10.14.5). I get this:
>>
>
> > import urllib.parse as urlparse
>
> You must be running Python 3.6 or above.
>
> 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/27fe6d24-124e-402a-9100-e5db000a733c%40googlegroups.com.

Re: Linux Snapcraft and Packager integrations are broken

[Chris George]

I will take a run at snapcraft.

My distro has it installed by default.

Chris

On Thu, Jul 25, 2019 at 1:23 PM Matt Wilkie  wrote:

> The Leo Github Webhooks
>  page has two
> failing integrations: snapcraft.io and packager.io.
>
> From a quick inspection it looks like they're supposed to be for building
> complete Linux packages to install. Does anyone want to take these over or
> should we remove the hooks?
>
> -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/eec27254-f164-45d6-a681-02a46a09351d%40googlegroups.com
> 
> .
>

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

Linux Snapcraft and Packager integrations are broken

[Matt Wilkie]

The Leo Github Webhooks 
 page has two 
failing integrations: snapcraft.io and packager.io.

>From a quick inspection it looks like they're supposed to be for building 
complete Linux packages to install. Does anyone want to take these over or 
should we remove the hooks?

-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/eec27254-f164-45d6-a681-02a46a09351d%40googlegroups.com.

Re: ENB: Harmonize Leo and Pip version numbers (#1242)

[Matt Wilkie]

> > pip show leo
> Name: leo
> Version: 6.0b1.dev103
>
>
It's an error to compare pip show and leo --version. This is because pip 
show reveals the *version number when pip install -e was run, not what the 
current editable version is*. To report the actual current editiable 
version is use:

> python setup.py --version

Creating entry_points for [OS name - system]: nt - Windows
c:\tools\miniconda3\envs\leo-dev\lib\site-packages\setuptools\dist.py:470: 
UserWarning: Normalizing '6.0b1-dev112' to '6.0b1.dev112'
  normalized_version,

6.0b1.dev112

-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/2d143294-13cc-476b-b2ea-03d56a005ee4%40googlegroups.com.

Re: ENB: Harmonize Leo and Pip version numbers (#1242)

[Matt Wilkie]

>
> Feel free to update the checklist in leoDist.leo, if you have not already 
> done so.  It would be a good idea to explain why this step is necessary.  
> In other words, don't rely on my memory ;-)
>

Done, with commit 7ce1b76 

 
.

QQQ
Matt: After merge create dev tag that matches static version added to 
leoversion.py 4 steps ago.  
#static version = '6.0-b2-devel'

git checkout devel
git tag -a v6.0-b2-dev -m "Added v6.0-b2-dev tag"
git push --follow-tags
QQQ

I dithered over whether the tag should have "dev" suffix, because it's in 
the devel branch after all. In end I decided to included it because 
eventually there will be a b2 *release*, which would then be tagged "v6.0-b2
"

-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/82e3d184-9ddf-4f36-b774-97b256959538%40googlegroups.com.

Tip: faster dev pip installs with shallow clones

[Matt Wilkie]

*Things I learned today.*

When running `pip install --editable path/to/leo` the  *"Installing build 
dependencies ..."* step can take a lng time. Apparently this is because 
it creates a copy of the folder tree including the `.git` folder, which can 
be quite large (ref ). My machine 
right now: .git is 183 MB, while Leo is only 40 MB.

Solution: periodically create a new leo-editor shallow clone 
:

cd d:\code
git clone --depth=100 https://github.com/leo-editor/leo-editor.git 
d:/code/shallow-leo-editor
move d:\code\leo-editor d:\code\leo-editor-bloated
move d:\code\shallow-leo-editor d:\code\leo-editor


At current commit rate

   - depth=100 is 6 months of history and 60mb (.git & Leo together)
   - depth=500 is 2 years and 73 MB
   - depth={infinity} is 11 years and 242 MB


-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/18ed34c5-7a72-404e-9ee1-b6565710f06c%40googlegroups.com.

Re: Mac import error after update

[Edward K. Ream]

On Thu, Jul 25, 2019 at 6:31 AM Rob  wrote:

> Since the last big Leo upgrade in June, I can't get it to start on macOS
> Mojave (10.14.5). I get this:
>

> import urllib.parse as urlparse

You must be running Python 3.6 or above.

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/CAMF8tS3iSCr6n%3Dx2za3Z5FCt0tsCOz-W9z90Vi0who2Q-6uhpQ%40mail.gmail.com.

Mac import error after update

[Rob]

Since the last big Leo upgrade in June, I can't get it to start on macOS 
Mojave (10.14.5). I get this:

Traceback (most recent call last):

  File "launchLeo.py", line 7, in 

import leo.core.runLeo

  File "/Users/rkeeney/leo-editor/leo/core/runLeo.py", line 25, in 

import leo.core.leoGlobals as leoGlobals

  File "/Users/rkeeney/leo-editor/leo/core/leoGlobals.py", line 68, in 


import urllib.parse as urlparse

ImportError: No module named parse

It's probably something simple like updating pyQT or something, but don't 
know how to do that on Mac. Any suggestions?

Rob...

-- 
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/1df9a63c-9155-42f0-af93-edf0c0876eb8%40googlegroups.com.

Re: ENB: Harmonize Leo and Pip version numbers (#1242)

[Edward K. Ream]

On Thu, Jul 25, 2019 at 12:15 AM Matt Wilkie  wrote:

>
> *Engineering notebook post about "Harmonize Leo and Pip version numbers
> #1242 ". Much of this
> opening post to mailing list is copied from the issue description. I
> realized it's better to have the "thinking out loud" parts in the mailing
> list, where people can chime in more easily, *
>

I agree.  I use the first comment of an issue to summarize the status of
each issue.  That is, I freely edit the first comment to keep it up to date.

Imo, thinking out loud should be done in public whenever possible.

> So is all that's needed is to add:
>
>1. create git tag for v6.0-b2-dev in devel branch?
>
> I'm not sure it fits, because of the backward looking nature. ...still
> thinking...
>
> [many git-reading hours later]: yes, I think this is a good idea. At the
> cost of adding yet-another-step for the human in the Creating a Release
> workflow.
>
Excellent work.  The extra step is a small price to pay for resolving this
issue.

Feel free to update the checklist in leoDist.leo, if you have not already
done so.  It would be a good idea to explain why this step is necessary.
In other words, don't rely on my memory ;-)

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/CAMF8tS1iQsSEw0ZL8%3DP%2B5yNY2QoUk6f2zrE5SjcjQs2Xm2AVxg%40mail.gmail.com.