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]
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
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
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
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
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
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,
Hi,
Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872052
could you suppoort python3.8 python3.7 and pyhton3.6 ?
Thanks