On Dec 11, 2019, at 17:33, Stephen John Smoogen wrote:
> I want to correct one thing: EPEL is not an Enterprise repository. It
> is a nearly complete volunteer effort and things will add and
> disappear over time as volunteers come in and out. We try to make it
> stable and useful but we do not
On Wed, 11 Dec 2019 at 17:23, Fred Gleason wrote:
>
> On Dec 11, 2019, at 12:50, Stephen John Smoogen wrote:
>
> The issue is that most 'users' of the language do not see a difference
> between the 2. When they say python3x they mean
> python3x+whatever-bits-i-needed. So as soon as you put in
On Dec 11, 2019, at 12:50, Stephen John Smoogen wrote:
> The issue is that most 'users' of the language do not see a difference
> between the 2. When they say python3x they mean
> python3x+whatever-bits-i-needed. So as soon as you put in the
> interpreter.. then comes the 'why isn't python37-x
On Wed, 11 Dec 2019 at 11:44, Miro Hrončok wrote:
>
> On 11. 12. 19 17:01, Stephen John Smoogen wrote:
> > On Tue, 10 Dec 2019 at 20:24, Miro Hrončok wrote:
> >>
> >> Hey EPEL people.
> >>
> >> We got a request to branch Python 3.7 foe EPEL 7:
> >>
> >>
On 11. 12. 19 17:01, Stephen John Smoogen wrote:
On Tue, 10 Dec 2019 at 20:24, Miro Hrončok wrote:
Hey EPEL people.
We got a request to branch Python 3.7 foe EPEL 7:
https://bugzilla.redhat.com/show_bug.cgi?id=1781940
Are there volunteers to make that effort? And if so, should this be done
On Tue, 10 Dec 2019 at 20:24, Miro Hrončok wrote:
>
> Hey EPEL people.
>
> We got a request to branch Python 3.7 foe EPEL 7:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1781940
>
> Are there volunteers to make that effort? And if so, should this be done in
> EPEL
> 8 first? And what about
