bug#28160: Support newer version of python

2018-03-08 Thread Mathieu Lirzin
Mathieu Lirzin writes: > Here is an alternative patch to fixes this bug, that I intend to push > tomorrow. > >>From 88df0576249df21e719ff3ac95d3d27b77e3370f Mon Sep 17 00:00:00 2001 > From: Mathieu Lirzin > Date: Sat, 3 Mar 2018 12:01:13 +0100 > Subject: [PATCH] python: Support future python ver

bug#28160: Support newer version of python

2018-03-03 Thread Mathieu Lirzin
Hello, Mathieu Lirzin writes: > Mathieu Lirzin writes: > From 1d60fb72168e62d33fe433380af621de64e22f23 Mon Sep 17 00:00:00 2001 >> From: Mathieu Lirzin >> Date: Thu, 1 Feb 2018 13:51:03 +0100 >> Subject: [PATCH] python: Generate python interpreter list >> >> _AM_PYTHON_INTERPRETER_LIST is

bug#28160: Support newer version of python

2018-02-18 Thread Mathieu Lirzin
Mathieu Lirzin writes: >>From 1d60fb72168e62d33fe433380af621de64e22f23 Mon Sep 17 00:00:00 2001 > From: Mathieu Lirzin > Date: Thu, 1 Feb 2018 13:51:03 +0100 > Subject: [PATCH] python: Generate python interpreter list > > _AM_PYTHON_INTERPRETER_LIST is used by AM_PYTHON_PATH to autodetect > Pyth

bug#28160: Support newer version of python

2018-02-03 Thread Mathieu Lirzin
Hello, Mathieu Lirzin writes: >>> On 09/15/17 11:17, Mathieu Lirzin wrote: Instead of preemptively adding possible future version of Python that hopefully would be released, I would prefer a solution that removes the need to hard-code them. > > It seems that GNU Pyconfigure has al

bug#28160: Support newer version of python

2017-09-22 Thread Mathieu Lirzin
Hello, Moritz Klammler writes: > On 09/15/2017 11:42 AM, Thomas Jahns wrote: >> On 09/15/17 11:17, Mathieu Lirzin wrote: >>> Instead of preemptively adding possible future version of Python that >>> hopefully would be released, I would prefer a solution that removes the >>> need to hard-code the

bug#28160: Support newer version of python

2017-09-15 Thread Moritz Klammler
On 09/15/2017 11:42 AM, Thomas Jahns wrote: > On 09/15/17 11:17, Mathieu Lirzin wrote: >> Instead of preemptively adding possible future version of Python that >> hopefully would be released, I would prefer a solution that removes the >> need to hard-code them. >> >> WDYT? > > Why not parse PATH a

bug#28160: Support newer version of python

2017-09-15 Thread Thomas Jahns
On 09/15/17 11:17, Mathieu Lirzin wrote: Instead of preemptively adding possible future version of Python that hopefully would be released, I would prefer a solution that removes the need to hard-code them. WDYT? Why not parse PATH and filter what pathelem/python* returns for a pattern like p

bug#28160: Support newer version of python

2017-09-15 Thread Mathieu Lirzin
Hello Bastien, Bastien ROUCARIES writes: > Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872052 > could you suppoort python3.8 python3.7 and python3.6 ? Python 3.6 is already added In last release 1.15.1. Since Python 3.7 and 3.8 are not release yet, I am not comfortable adding t

bug#28160: Support newer version of python

2017-08-20 Thread Bastien ROUCARIES
Hi, Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872052 could you suppoort python3.8 python3.7 and pyhton3.6 ? Thanks