On 2015-10-14, Scott Kostyshak wrote:
> On Fri, Dec 19, 2014 at 11:26:35AM -0500, Scott Kostyshak wrote:
>> On Fri, Dec 19, 2014 at 4:40 AM, Benjamin Piwowarski
>> wrote:
...
>> > sorry for the long delay - I started to clean up python scripts to
>> > make them compatible
On Fri, Dec 19, 2014 at 11:26:35AM -0500, Scott Kostyshak wrote:
> On Fri, Dec 19, 2014 at 4:40 AM, Benjamin Piwowarski wrote:
> > Hi to all,
> >
> > sorry for the long delay - I started to clean up python scripts to make them
> > compatible with both python 2 and 3 so there are
Hi to all,
sorry for the long delay - I started to clean up python scripts to make
them compatible with both python 2 and 3 so there are no more issues with
this. I was stopped by lack of time but will start to look at that again -
it is not such a big amount of work.
Benjamin
On Fri, Nov 21,
On Friday 19 December 2014 10:40:00 Benjamin Piwowarski wrote:
Hi to all,
sorry for the long delay - I started to clean up python scripts to make
them compatible with both python 2 and 3 so there are no more issues with
this. I was stopped by lack of time but will start to look at that again
On Fri, Dec 19, 2014 at 4:40 AM, Benjamin Piwowarski bpiwo...@lyx.org wrote:
Hi to all,
sorry for the long delay - I started to clean up python scripts to make them
compatible with both python 2 and 3 so there are no more issues with this. I
was stopped by lack of time but will start to look
Hi to all,
sorry for the long delay - I started to clean up python scripts to make
them compatible with both python 2 and 3 so there are no more issues with
this. I was stopped by lack of time but will start to look at that again -
it is not such a big amount of work.
Benjamin
On Fri, Nov 21,
On Friday 19 December 2014 10:40:00 Benjamin Piwowarski wrote:
> Hi to all,
>
> sorry for the long delay - I started to clean up python scripts to make
> them compatible with both python 2 and 3 so there are no more issues with
> this. I was stopped by lack of time but will start to look at that
On Fri, Dec 19, 2014 at 4:40 AM, Benjamin Piwowarski wrote:
> Hi to all,
>
> sorry for the long delay - I started to clean up python scripts to make them
> compatible with both python 2 and 3 so there are no more issues with this. I
> was stopped by lack of time but will start
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own bundled python2 and it works fine. The
problem arises when I want to import my python graphics into LyX,
which should be interpreted
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own bundled python2 and it works fine. The
problem arises when I want to import my python
Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck rgh...@lyx.org
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own
On 11/21/2014 09:23 AM, Kornel Benko wrote:
Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck rgh...@lyx.org
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I
Richard Heck wrote:
It might be possible to specify the full path to the python version you
want to use in
the relevant converter definition. But I am not sure.
This is possible. The magic happens only for python -tt. Even specifying
only python3 or python3 -tt as the interpreter for self
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own bundled python2 and it works fine. The
problem arises when I want to import my python graphics into LyX,
which should be interpreted
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own bundled python2 and it works fine. The
problem arises when I want to import my python
Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck
> On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
> > Ok, let me be splicit. I use extensively Spyder with python 3 for my
> > work, I use also LyX to write my articles. When I installed LyX (on
> > windows) it uses
On 11/21/2014 09:23 AM, Kornel Benko wrote:
Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I
Richard Heck wrote:
> It might be possible to specify the full path to the python version you
> want to use in
> the relevant converter definition. But I am not sure.
This is possible. The magic happens only for "python -tt". Even specifying
only "python3" or "python3 -tt" as the interpreter
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be run under Python 2 and will not work properly on systems
where Python 3 is the default binary. See bug #7030 to know how to fix
this properly, since simple sheebang conversion in *.py files
On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak skost...@lyx.org wrote:
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be run under Python 2 and will not work properly on systems
where Python 3 is the default binary. See bug #7030 to know
The incompatibilities still exist at least in Windows sistems, since
LyX installer bundles a python distribution itself and creates a
conflict when python3 is the default. Moreover you cannot use python3
within LyX in Windows, because you will beak the system, LyX will not
reconfigure anymore!!
On 11/20/2014 09:55 AM, stefano franchi wrote:
On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak skost...@lyx.org
mailto:skost...@lyx.org wrote:
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be run under Python 2 and will not work
On Thu, Nov 20, 2014 at 11:36 AM, Richard Heck rgh...@lyx.org wrote:
On 11/20/2014 09:55 AM, stefano franchi wrote:
On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak skost...@lyx.org wrote:
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be run under Python 2 and will not work properly on systems
where Python 3 is the default binary. See bug #7030 to know how to fix
this properly, since simple sheebang conversion in *.py files
On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak wrote:
> I cleaned RELEASE-NOTES for the master branch. This note is still
> relevant right?
>
> - LyX needs to be run under Python 2 and will not work properly on systems
> where Python 3 is the default binary. See bug #7030
The incompatibilities still exist at least in Windows sistems, since
LyX installer bundles a python distribution itself and creates a
conflict when python3 is the default. Moreover you cannot use python3
within LyX in Windows, because you will beak the system, LyX will not
reconfigure anymore!!
On 11/20/2014 09:55 AM, stefano franchi wrote:
On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak > wrote:
I cleaned RELEASE-NOTES for the master branch. This note is still
relevant right?
- LyX needs to be run under Python 2 and will not
On Thu, Nov 20, 2014 at 11:36 AM, Richard Heck wrote:
> On 11/20/2014 09:55 AM, stefano franchi wrote:
>
> On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak wrote:
>
>> I cleaned RELEASE-NOTES for the master branch. This note is still
>> relevant right?
>>
>> -
28 matches
Mail list logo