Re: prefs2prefs.py not compatible with python3 [PATCH]

On Sat, Apr 08, 2017 at 08:59:04PM +0200, Stephan Witt wrote: > Am 06.04.2017 um 03:10 schrieb Scott Kostyshak : > > > > On Sat, Apr 01, 2017 at 09:49:13AM +0100, José Abílio Matos wrote: > >> On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote: > >>> José, any

Re: prefs2prefs.py not compatible with python3 [PATCH]

Am 06.04.2017 um 03:10 schrieb Scott Kostyshak : > > On Sat, Apr 01, 2017 at 09:49:13AM +0100, José Abílio Matos wrote: >> On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote: >>> José, any thoughts? >> >> The changes are reasonable and in line with what has been done

Re: prefs2prefs.py not compatible with python3 [PATCH]

On Sat, Apr 01, 2017 at 09:49:13AM +0100, José Abílio Matos wrote: > On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote: > > José, any thoughts? > > The changes are reasonable and in line with what has been done in other > places. > So if it works for both python 2 and 3 it should go

Re: prefs2prefs.py not compatible with python3 [PATCH]

On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote: > José, any thoughts? The changes are reasonable and in line with what has been done in other places. So if it works for both python 2 and 3 it should go in. :-) -- José Abílio

Re: prefs2prefs.py not compatible with python3 [PATCH]

On Sun, Jan 15, 2017 at 09:22:24PM +0100, pdv wrote: > On 15/01/17 19:28, Stephan Witt wrote: > > Am 15.01.2017 um 19:07 schrieb Stephan Witt : > > > > > > Am 15.01.2017 um 17:10 schrieb Stephan Witt : > > > > > > > > Am 15.01.2017 um 13:44 schrieb pdv

Re: prefs2prefs.py not compatible with python3 [PATCH]

On 15/01/17 19:28, Stephan Witt wrote: Am 15.01.2017 um 19:07 schrieb Stephan Witt : Am 15.01.2017 um 17:10 schrieb Stephan Witt : Am 15.01.2017 um 13:44 schrieb pdv : On 15/01/17 00:11, Stephan Witt wrote: Am 15.01.2017 um 00:05

Re: prefs2prefs.py not compatible with python3 [PATCH]

Am 15.01.2017 um 19:07 schrieb Stephan Witt : > > Am 15.01.2017 um 17:10 schrieb Stephan Witt : >> >> Am 15.01.2017 um 13:44 schrieb pdv : >>> >>> On 15/01/17 00:11, Stephan Witt wrote: Am 15.01.2017 um 00:05 schrieb Stephan Witt

Re: prefs2prefs.py not compatible with python3 [PATCH]

Am 15.01.2017 um 17:10 schrieb Stephan Witt : > > Am 15.01.2017 um 13:44 schrieb pdv : >> >> On 15/01/17 00:11, Stephan Witt wrote: >>> Am 15.01.2017 um 00:05 schrieb Stephan Witt : Am 14.01.2017 um 17:42 schrieb pdv

Re: prefs2prefs.py not compatible with python3

Am 15.01.2017 um 13:44 schrieb pdv : > > On 15/01/17 00:11, Stephan Witt wrote: >> Am 15.01.2017 um 00:05 schrieb Stephan Witt : >>> >>> Am 14.01.2017 um 17:42 schrieb pdv : The current master fails to start-up (on macOS)

Re: prefs2prefs.py not compatible with python3

On 15/01/17 00:11, Stephan Witt wrote: Am 15.01.2017 um 00:05 schrieb Stephan Witt : Am 14.01.2017 um 17:42 schrieb pdv : The current master fails to start-up (on macOS) if the default Python is Python3.x, because prefs2prefs.py is not compatible with

Re: prefs2prefs.py not compatible with python3

Am 15.01.2017 um 00:05 schrieb Stephan Witt : > > Am 14.01.2017 um 17:42 schrieb pdv : >> >> The current master fails to start-up (on macOS) if the default Python is >> Python3.x, because prefs2prefs.py is not compatible with Python3. > > This looks

Re: prefs2prefs.py not compatible with python3

Am 14.01.2017 um 17:42 schrieb pdv : > > The current master fails to start-up (on macOS) if the default Python is > Python3.x, because prefs2prefs.py is not compatible with Python3. This looks strange. The python people say python 2.7 is the default on Mac (including the

prefs2prefs.py not compatible with python3

The current master fails to start-up (on macOS) if the default Python is Python3.x, because prefs2prefs.py is not compatible with Python3. In python23() in os.cpp both Python 2 and Python 3 are accepted. As a temporarily workaround I've built with PYTHON="/usr/bin/python" which is the