configure.py assumes "python" command exists
Stephan Witt
st.witt at gmx.net
Wed Dec 29 11:59:07 UTC 2021
Am 27.12.2021 um 20:30 schrieb José Abílio Matos <jamatos at lyx.org>:
>
> On Saturday, 25 December 2021 18.32.21 WET Scott Kostyshak wrote:
> > On Sun, Oct 31, 2021 at 12:58:19PM -0400, Scott Kostyshak wrote:
>
> Hi Scott,
> I find you choice of dates very convenient. :-)
>
> https://journeys.dartmouth.edu/folklorearchive/2016/11/12/halloween-and-christmas/
>
> “Why do programmers always mix up Halloween and Christmas?”
> “Because Oct 31 = Dec 25.”
>
> > Bump.
> >
> > Scott
>
> Regarding the problem at hand, as an example, my suggestion is to change:
>
> \converter pdf4 pdf8 "python $$s/scripts/convert_pdf.py $$i $$o ebook"
>
> to
>
> \converter pdf4 pdf8 "$${python} $$s/scripts/convert_pdf.py $$i $$o ebook"
>
> The idea is to use the converter code, e.g. the $$i $$o ..., and add there the substitution from $${python} to the python path that we have already determined in os::find_python.
I like your proposal.
Regarding the use of python calls in configure.py I’ve stolen your idea to use sys.executable and made a patch.
This avoids the warning '„LyX“ needs to be updated‘ (see my RFC mail thread) and lyx starts as usual if I install python3 at first (https://www.python.org/downloads/release/python-3101)
Stephan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-in-configure.patch
Type: application/octet-stream
Size: 672 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20211229/700fba9f/attachment.obj>
More information about the lyx-devel
mailing list