On 2018-08-09 08:23, Miro Hrončok wrote:
On 8.8.2018 17:43, John Florian wrote:
On 2018-08-08 10:47, Jason Tibbitts wrote:
"JF" == John Florian writes:
JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
JF> in EPEL?
Obviously not that difficult, since it is already
On 8.8.2018 17:43, John Florian wrote:
On 2018-08-08 10:47, Jason Tibbitts wrote:
"JF" == John Florian writes:
JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
JF> in EPEL?
Obviously not that difficult, since it is already there.
By that I assume you mean 34, right?
On 8 August 2018 at 11:43, John Florian wrote:
> On 2018-08-08 10:47, Jason Tibbitts wrote:
>>>
>>> "JF" == John Florian writes:
>>
>> JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
>> JF> in EPEL?
>>
>> Obviously not that difficult, since it is already there.
>
>
On 2018-08-08 10:47, Jason Tibbitts wrote:
"JF" == John Florian writes:
JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
JF> in EPEL?
Obviously not that difficult, since it is already there.
By that I assume you mean 34, right? Or am I overlooking something?
The
> "JF" == John Florian writes:
JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
JF> in EPEL?
Obviously not that difficult, since it is already there. The main
problem is that the way it was done requires that Fedora specfiles grow
additional complication in order to
On 7.8.2018 16:26, Miro Hrončok wrote:
Available in updates-testing, please karma it:
https://bodhi.fedoraproject.org/updates/python35-3.5.6-1.fc28
https://bodhi.fedoraproject.org/updates/python35-3.5.6-1.fc27
https://bodhi.fedoraproject.org/updates/python34-3.4.9-1.fc28
