Vili,

On Sun, Feb 21, 2021 at 11:58 AM vili <viljem.tisni...@gmail.com> wrote:

> No problem with directories. But, it doesnt work this way on Mac. As I
> pointed out, there is system Python2 preinstalled on Mac by Apple. It is
> called by first row in the "runLeo.py" which reads:
>
> #! /usr/bin/env python
>

If the runLeo.py has the executable bit set and you try executing it
directly, then that first line (commonly called the shebang line) will be
used to execute the file. However if you are invoking python yourself and
passing this runLeo.py file as an argument, then python will ignore that
line because it is a comment. Therefore if you invoke python3 directly,
this line should not be the source of your trouble.

This is the last concrete output you shared related to invoking python3
directly:

vili@Viljems-MBP-2 leo-editor % python3 core/runLeo.py
/Library/Frameworks/Python.framework/Versions/3.9/bin/python3: can't open
file '/Users/vili/leo-editor/core/runLeo.py': [Errno 2] No such file or
directory


As Thomas rightly diagnosed, that error message is telling you that the
file 'core/runLeo.py' does not exist. But you didn't share any details on
what went wrong when you tried with the correct filename.

What error do you get when you run with the correct filename suggested by
Thomas:

cd leo-editor
python3 leo/core/runLeo.py


or since it looks like your leo-editor directory is child of your home
directory, you could run it like this (the tilde expands to your home
directory):

python3 ~/leo-editor/leo/core/runLeo.py


Whatever issue you have with that should have nothing to do with the
shebang line: '#! /usr/bin/env python'.

Brian

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

Reply via email to