Re: Python 2 in release notes

2016-05-21 Thread Scott Kostyshak
On Sat, May 21, 2016 at 10:16:25AM +0200, Georg Baum wrote: > José Matos wrote: > > > On Monday, May 9, 2016 9:46:01 PM WEST Scott Kostyshak wrote: > >> Georg or José, please feel free to make changes to the RELEASE-NOTES > >> regarding Python if you think it would make things more clear. > >> >

Re: Python 2 in release notes

2016-05-21 Thread Georg Baum
José Matos wrote: > On Monday, May 9, 2016 9:46:01 PM WEST Scott Kostyshak wrote: >> Georg or José, please feel free to make changes to the RELEASE-NOTES >> regarding Python if you think it would make things more clear. >> >> Scott > > I think that Georg's formulation is clear and more correct t

Re: Python 2 in release notes

2016-05-12 Thread José Matos
On Monday, May 9, 2016 9:46:01 PM WEST Scott Kostyshak wrote: > Georg or José, please feel free to make changes to the RELEASE-NOTES > regarding Python if you think it would make things more clear. > > Scott I think that Georg's formulation is clear and more correct than what we have now. Regar

Re: Python 2 in release notes

2016-05-09 Thread Scott Kostyshak
On Mon, May 09, 2016 at 05:25:40PM +0100, José Matos wrote: > On Saturday, May 7, 2016 11:39:32 AM WEST Georg Baum wrote: > > I am unsure about building LyX where "python" is python 3. We fixed some > > build scripts to work both with python 2 and 3, but maybe there are others > > that don't work

Re: Python 2 in release notes

2016-05-09 Thread José Matos
On Saturday, May 7, 2016 11:39:32 AM WEST Georg Baum wrote: > I am unsure about building LyX where "python" is python 3. We fixed some > build scripts to work both with python 2 and 3, but maybe there are others > that don't work with python 3 yet. Assuming that Helge confirms the fix for > conf

Python 2 in release notes

2016-05-07 Thread Georg Baum
lib/RELEASE-NOTES contains the following paragraph: * LyX needs to be run under Python 2 and will not work properly on systems where Python 3 is the default binary. See #7030 to know how to fix this properly, since simple shebang conversion in *.py files will not be enough. I believe that th