On Mon, Jun 01, 2020 at 11:07:39PM +0200, Michał Górny wrote:
> On Mon, 2020-06-01 at 15:49 -0500, Matthias Maier wrote:
> > On Mon, Jun 1, 2020, at 15:27 CDT, Michał Górny wrote:
> >
> > > 2020-08-01 Python 3.7 migration deadline
> > >
> > >After this date, we lastrite all remaining packa
On Mon, 01 Jun 2020 23:04:38 +0200
Michał Górny wrote:
> On Mon, 2020-06-01 at 13:34 -0700, Patrick McLean wrote:
> > On Mon, 01 Jun 2020 22:27:19 +0200
> > Michał Górny wrote:
> >
> > > Hi, everyone.
> > >
> > > I'd like to be more proactive in avoiding the mess like Python 3.6->3.7
> > > s
On Mon, 2020-06-01 at 15:49 -0500, Matthias Maier wrote:
> On Mon, Jun 1, 2020, at 15:27 CDT, Michał Górny wrote:
>
> > 2020-08-01 Python 3.7 migration deadline
> >
> >After this date, we lastrite all remaining packages that haven't been
> >ported. This gives people roughly two months
On Mon, 2020-06-01 at 13:34 -0700, Patrick McLean wrote:
> On Mon, 01 Jun 2020 22:27:19 +0200
> Michał Górny wrote:
>
> > Hi, everyone.
> >
> > I'd like to be more proactive in avoiding the mess like Python 3.6->3.7
> > switch were. For this reason, I think it would be better to set
> > and pub
On Mon, Jun 1, 2020, at 15:27 CDT, Michał Górny wrote:
> 2020-08-01 Python 3.7 migration deadline
>
>After this date, we lastrite all remaining packages that haven't been
>ported. This gives people roughly two months, with a ping one month
>from now.
> [...]
> 2020-12-01 Python
On Mon, 01 Jun 2020 22:27:19 +0200
Michał Górny wrote:
> Hi, everyone.
>
> I'd like to be more proactive in avoiding the mess like Python 3.6->3.7
> switch were. For this reason, I think it would be better to set
> and publish some early deadlines. Even if we aren't going to strictly
> keep to
Hi, everyone.
I'd like to be more proactive in avoiding the mess like Python 3.6->3.7
switch were. For this reason, I think it would be better to set
and publish some early deadlines. Even if we aren't going to strictly
keep to them, it would help people realize how much time there is left
to fi
