Discussion:
Python minimum versions for lyx-2.2
José Matos
2014-05-17 14:41:41 UTC
Permalink
Hi,
my name is José and I am a Lyxoholic. :-)

As part of the discussion that has been going for some time regarding the development of lyx-2.2, that in another thread I will propose to be instead called 2.2718281828459045 or as a better shortcut LyX 2e, I would like to settle the question regarding the minimum version supported.

My suggestion, as stated several times in that thread is to go with python 2.7 or python 3.3+.

That is from python 2 we will support only python 2.7 and from the python 3 series we will support python 3.3 and later.

The idea is also to have the same code to be able to support both python 2 and python 3, for that I intend to add further documentation to the devel directory regarding the best advice to do it. That includes, but is not limited to, using

from __future__ import absolute_import, division, print_function

The purpose of this message is then to settle the issue and to let us concentrate from here on the technicalities to fulfill this goal.

Feedback is appreciated. Regards,

PS: As stated before I will start to handle this in June.
--
José Abílio
Enrico Forestieri
2014-05-17 21:39:36 UTC
Permalink
Post by José Matos
Hi,
my name is José and I am a Lyxoholic. :-)
Have you tried some AUCTeX pills or the TeXmacs elixir?
Post by José Matos
As part of the discussion that has been going for some time regarding the
development of lyx-2.2, that in another thread I will propose to be
instead called 2.2718281828459045 or as a better shortcut LyX 2e, I would
like to settle the question regarding the minimum version supported.
Nah, that would be lyx-4.543656365691809 ;)
Post by José Matos
My suggestion, as stated several times in that thread is to go with
python 2.7 or python 3.3+.
Seems reasonable.
--
Enrico
José Matos
2014-05-21 10:43:57 UTC
Permalink
Post by Enrico Forestieri
Have you tried some AUCTeX pills or the TeXmacs elixir?
With two kids I don't need any pills to sleep, not that I needed it before either. :-)
--
José Abílio
Stephan Witt
2014-05-18 11:22:10 UTC
Permalink
Post by José Matos
Hi,
my name is José and I am a Lyxoholic. :-)
Hi José, I'm Stephan from Berlin. I hope that you'll remember me :-)
Post by José Matos
As part of the discussion that has been going for some time regarding the development of lyx-2.2, that in another thread I will propose to be instead called 2.2718281828459045 or as a better shortcut LyX 2e, I would like to settle the question regarding the minimum version supported.
My suggestion, as stated several times in that thread is to go with python 2.7 or python 3.3+.
That is from python 2 we will support only python 2.7 and from the python 3 series we will support python 3.3 and later.
The idea is also to have the same code to be able to support both python 2 and python 3, for that I intend to add further documentation to the devel directory regarding the best advice to do it. That includes, but is not limited to, using
from __future__ import absolute_import, division, print_function
The purpose of this message is then to settle the issue and to let us concentrate from here on the technicalities to fulfill this goal.
Feedback is appreciated. Regards,
I just tried python 2.7.6 on Mac OS X 10.5.8 (Leopard).

The installation is easy if one downloads the appropriate file.
The big fat download button retrieves the wrong on (for 10.6 or better).

The installation of the package adjusts the environment accordingly and
makes the new 2.7.6 python the default one.

For Mac OS X 10.5.8 I can confirm it was easy to upgrade to python 2.7.6.
So, this wouldn't be a spoilsport. For 10.6 I'd expect the same result.

Stephan
José Matos
2014-05-21 10:42:48 UTC
Permalink
Post by Stephan Witt
Hi José, I'm Stephan from Berlin. I hope that you'll remember me
Sure I do. :-)

BTW I still remember the tasty coffee we got at your place. :-)
Post by Stephan Witt
I just tried python 2.7.6 on Mac OS X 10.5.8 (Leopard).
The installation is easy if one downloads the appropriate file.
The big fat download button retrieves the wrong on (for 10.6 or better).
The installation of the package adjusts the environment accordingly and
makes the new 2.7.6 python the default one.
For Mac OS X 10.5.8 I can confirm it was easy to upgrade to python 2.7.6.
So, this wouldn't be a spoilsport. For 10.6 I'd expect the same result.
Thanks for the note. That was also my expectation.
Post by Stephan Witt
Stephan
--
José Abílio
Loading...