Am 28.12.2021 um 13:55 schrieb José Abílio Matos <jama...@lyx.org>:
> 
> On Tuesday, 28 December 2021 12.33.57 WET Stephan Witt wrote:
> > The LyX tasks here are IMO:
> > 1. Assure the detected python3 is used consequently. This is not the case
> > ATM.
> > 2. Document the meaning of the prompts the LyX user is seeing on
> > Monterey.
> > 3. Provide a working python3 or give appropriate feedback on
> > first start about users option to install python3.
> >
> > AFAIK, José Abílio is working on a solution for 1. I’m able to help with the
> > Mac part of the problem.
> 
> I am not working on 1, the issue that I am working is a bit different, 
> although related.

I referred to your proposal to consequently use the detected python version in 
our scripts.

ATM on Mac with python3 installed there are hardcoded calls of python e.g. in 
configure.py
or - as you’ve pointed out - in the generated converter calls triggering the 
warning
„LyX“ needs to be updated we want to avoid.

> In the case of mac we can
> What I suggest is to use by default the latest python version available in 
> the system.

That’s part of the problem. „Virgin“ systems have python 2 only.

> As it is now we search for a python version and stick with it.
> What I propose is to test the different versions available and pick the 
> latest.
> 
> Python 3 has been tested extensively and so it is ready to be the default 
> option.

Yes, I agree.

> > Regarding the point 3 - Apples recommendation to bundle python with LyX
> > (49764202) - I’m not sure if this is a real option. The Windows package
> > contains python, IMO. So it is possible. But is it clever? I don’t like the
> > solution to point the user to homebrew or macports to install python. Too
> > much terminal work, IMO.
> >
> > What do others think about the situation?
> 
> How do you deal with the latex installation in mac?

LyX starts fine w/o it and the user has to install some TeX distribution to use 
it.
There is a recommended one: MacTeX - having a installable disc image for 
download on it’s
web site. This is easy to use.

For Python the situation is a little bit different. The macOS „blames“ LyX at 
the first
configure run if the user didn’t install a recent python 3 already. Either we 
live with it
and document this near the download link at lyx.org or we try to inform the 
user at LyX
startup and give the opportunity to download and install python 3 and refuse to 
run configure
with the system python. This solves the problem we run into if Apple removes 
python altogether.

The homebrew or macports packages are the other option for experienced users. 
Some of them
have an installation on the system already. So we should detect it and be fine 
with it too.

In any case we should ensure the detected usable python is used consequently.

Stephan
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Reply via email to