lation;
> - warn if python2 cannot be found and ask the user to provide a path to a
> valid one.
I'd like to avoid nother rc entry. Nobody would understand anymore how the
system PATH, the LyX path prefix and the LyX python path would work
together, and which is allowed to be changed in which rc file (default, user
and dist).
Georg
Guenter Milde wrote:
> I propose to make all LyX's Python scripts compatible with both, Python 2
> and 3. For complex scripts, this could mean a version-test at runtime in
> a wrapper that subsequently imports the correct module or sets sys.path
> appropriately...
See the discussions in http://ww
On 16 Mar 2014 at 10:14:40 , Guenter Milde (mi...@users.sf.net) wrote:
On 2014-03-15, Benjamin Piwowarski wrote:
> This is related to bug http://www.lyx.org/trac/ticket/8950
> The problem is the following. Currently, to find python2, LyX:
> - checks the python command is a valid python 2 exec
On 2014-03-15, Benjamin Piwowarski wrote:
> This is related to bug http://www.lyx.org/trac/ticket/8950
> The problem is the following. Currently, to find python2, LyX:
> - checks the python command is a valid python 2 executable
> - if so, it just stores that the python command is “python” (othe
Hi,
This is related to bug http://www.lyx.org/trac/ticket/8950
The problem is the following. Currently, to find python2, LyX:
- checks the python command is a valid python 2 executable
- if so, it just stores that the python command is “python” (otherwise, it
searches and uses an absolute path
