Re: [PATCH 0/2] Update Python to current versions

2016-04-27 Thread Hartmut Goebel
Am 27.04.2016 um 18:55 schrieb Leo Famulari: > It should be possible to do these 3 actions without causing any packages > to be rebuilt. I think the first 2 steps should be in one commit, and > the second step in a second commit. > > [...] > This will require every python-3 package to be rebuilt, s

Re: [PATCH 0/2] Update Python to current versions

2016-04-27 Thread Leo Famulari
On Tue, Apr 26, 2016 at 11:28:53AM +0200, Hartmut Goebel wrote: > Am 24.04.2016 um 02:18 schrieb Leo Famulari: > > If we can successfully update to 3.5, that would be best. Otherwise, we > > should consider using 3.4.4. > > I disagree. > > While Python typically is backward-compatible (except for

Re: [PATCH 0/2] Update Python to current versions

2016-04-26 Thread Hartmut Goebel
Am 24.04.2016 um 02:18 schrieb Leo Famulari: > If we can successfully update to 3.5, that would be best. Otherwise, we > should consider using 3.4.4. I disagree. While Python typically is backward-compatible (except for the big change between Python 2 and Python 3), some minor incompatibilities a

Re: [PATCH 0/2] Update Python to current versions

2016-04-25 Thread Leo Famulari
On Sun, Apr 24, 2016 at 11:43:09PM +0200, Ludovic Courtès wrote: > Leo Famulari skribis: > > > On Fri, Apr 22, 2016 at 08:41:04AM +0200, Hartmut Goebel wrote: > >> Am 22.04.2016 um 01:12 schrieb Cyril Roelandt: > >> > I think the latest Python 3.x is Python 3.5.1 (see > >> > https://www.python.or

Re: [PATCH 0/2] Update Python to current versions

2016-04-24 Thread Ludovic Courtès
Leo Famulari skribis: > On Fri, Apr 22, 2016 at 08:41:04AM +0200, Hartmut Goebel wrote: >> Am 22.04.2016 um 01:12 schrieb Cyril Roelandt: >> > I think the latest Python 3.x is Python 3.5.1 (see >> > https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? >> >> Python 3.4.4 is the lat

Re: [PATCH 0/2] Update Python to current versions

2016-04-23 Thread Leo Famulari
On Fri, Apr 22, 2016 at 08:41:04AM +0200, Hartmut Goebel wrote: > Am 22.04.2016 um 01:12 schrieb Cyril Roelandt: > > I think the latest Python 3.x is Python 3.5.1 (see > > https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? > > Python 3.4.4 is the latest version fon the 3.4 series.

Re: [PATCH 0/2] Update Python to current versions

2016-04-21 Thread Hartmut Goebel
Am 22.04.2016 um 01:12 schrieb Cyril Roelandt: > I think the latest Python 3.x is Python 3.5.1 (see > https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? Python 3.4.4 is the latest version fon the 3.4 series. So we should provide this too. (Esp. as long as 3.5 ist not packaged yet)

Re: [PATCH 0/2] Update Python to current versions

2016-04-21 Thread Efraim Flashner
On Fri, Apr 22, 2016 at 01:12:38AM +0200, Cyril Roelandt wrote: > On 04/21/2016 10:18 PM, Hartmut Goebel wrote: > > gnu: python: Update to 3.4.4 > I think the latest Python 3.x is Python 3.5.1 (see > https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? > > Cyril. > I know there

Re: [PATCH 0/2] Update Python to current versions

2016-04-21 Thread Cyril Roelandt
On 04/21/2016 10:18 PM, Hartmut Goebel wrote: > gnu: python: Update to 3.4.4 I think the latest Python 3.x is Python 3.5.1 (see https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? Cyril.

[PATCH 0/2] Update Python to current versions

2016-04-21 Thread Hartmut Goebel
Update Python to current minor version Hartmut Goebel (2): gnu: python-2: Update to 2.7.11 gnu: python: Update to 3.4.4 gnu/packages/python.scm | 8 1 file changed, 4 insertions(+), 4 deletions(-) -- 2.7.4