On 27. 05. 22 12:07, Miro Hrončok wrote:
As I written this down, I think the better thing to do is to accept the gaps and
retire Python 3.7 before Python 3.6 right away and not decide to "keep it
around, as we still support both 3.6 and 3.8".
Thanks for all the answers.
I've created
On Fri, May 27, 2022 at 11:35 AM Miro Hrončok wrote:
>
> On 27. 05. 22 14:34, Neal Gompa wrote:
> > While unfortunate, I think it makes sense to retire Python 3.7 when
> > Debian 10 goes EOL.
>
> I don't understand why do you consider this unfortunate.
>
The situation is unfortunate, not the
On 27. 05. 22 14:34, Neal Gompa wrote:
While unfortunate, I think it makes sense to retire Python 3.7 when
Debian 10 goes EOL.
I don't understand why do you consider this unfortunate.
I think the larger question is how do we write
down a multi-Python maintenance policy to codify this?
It
On Fri, May 27, 2022 at 6:07 AM Miro Hrončok wrote:
>
> Hey Pythonistas,
>
> let me include you in my dilemma I have wrt different Python versions we
> support in Fedora for testing.
>
> tl;dr Should we retire Python 3.7 before Python 3.6? 3.6 will stick around for
> RHEL 8, but 3.7 will no
Hey Pythonistas,
let me include you in my dilemma I have wrt different Python versions we
support in Fedora for testing.
tl;dr Should we retire Python 3.7 before Python 3.6? 3.6 will stick around for
RHEL 8, but 3.7 will no longer be "needed". However, retiring mid-order might
be confusing.
