Re: Modularity, container images, and the default Python stack(s)

2017-08-29 Thread Nick Coghlan
On 29 August 2017 at 19:33, Petr Viktorin wrote: > On 08/25/2017 10:23 AM, Nick Coghlan wrote: >> Traditionally, that would have meant that we wouldn't get a Fedora >> based Python 3.7 container out the door until the release of Fedora 29 >> in October, and we'd never ship

Re: Modularity, container images, and the default Python stack(s)

2017-08-29 Thread Petr Viktorin
On 08/25/2017 10:23 AM, Nick Coghlan wrote: On 24 August 2017 at 21:28, Petr Viktorin wrote: On 08/24/2017 12:22 PM, Nick Coghlan wrote: Stream names match the Platform module. We follow its policy here, even when it changes. Oh, interesting, I had that backwards (I

Re: Modularity, container images, and the default Python stack(s)

2017-08-25 Thread Nick Coghlan
On 24 August 2017 at 21:28, Petr Viktorin wrote: > On 08/24/2017 12:22 PM, Nick Coghlan wrote: >>> Stream names match the Platform module. We follow its policy here, even >>> when >>> it changes. >> >> Oh, interesting, I had that backwards (I thought the planned F27 >> Python

Re: Modularity, container images, and the default Python stack(s)

2017-08-24 Thread Petr Viktorin
On 08/24/2017 12:22 PM, Nick Coghlan wrote: On 24 August 2017 at 19:02, Petr Viktorin wrote: On 08/24/2017 10:13 AM, Nick Coghlan wrote: My current thinking based on that discussion is that we're actually going to need a module set that looks like this for F28+: *

Re: Modularity, container images, and the default Python stack(s)

2017-08-24 Thread Nick Coghlan
On 24 August 2017 at 19:02, Petr Viktorin wrote: > On 08/24/2017 10:13 AM, Nick Coghlan wrote: >> My current thinking based on that discussion is that we're actually >> going to need a module set that looks like this for F28+: >> >> * Platform Python (already planned for F27)

Re: Modularity, container images, and the default Python stack(s)

2017-08-24 Thread Petr Viktorin
On 08/24/2017 10:13 AM, Nick Coghlan wrote: On 21 August 2017 at 19:46, Petr Viktorin wrote: On 08/18/2017 01:38 PM, Nick Coghlan wrote: Does that approach sound sufficiently plausible to folks that I can use it to provide feedback to the folks working on the modularity

Re: Modularity, container images, and the default Python stack(s)

2017-08-24 Thread Nick Coghlan
On 21 August 2017 at 19:46, Petr Viktorin wrote: > On 08/18/2017 01:38 PM, Nick Coghlan wrote: >> Does that approach sound sufficiently plausible to folks that I can >> use it to provide feedback to the folks working on the modularity >> tooling as to the capabilities we

Re: Modularity, container images, and the default Python stack(s)

2017-08-21 Thread Petr Viktorin
On 08/18/2017 01:38 PM, Nick Coghlan wrote: Hi folks, [Note: this may not make much sense to folks that haven't been closely following the Modular Server work for F27. If that's you, sorry - hopefully this will be more comprehensible by the time I officially propose it for F28, as the relevant

Modularity, container images, and the default Python stack(s)

2017-08-18 Thread Nick Coghlan
Hi folks, [Note: this may not make much sense to folks that haven't been closely following the Modular Server work for F27. If that's you, sorry - hopefully this will be more comprehensible by the time I officially propose it for F28, as the relevant terminology becomes more widely understood. In