[Python-modules-team] Bug#913424: Should python-trio be allowed into testing? (Was: state of python-msrest.)

[Robie Basak]

On Mon, Oct 21, 2019 at 12:57:38AM +0100, peter green wrote:
> It's not private, these mails were set to "python-msrest at packages.debian.org" which forwards to "python-modules-team at lists.alioth.debian.org". This mail thread can be found at https://alioth-lists.debian.net/pipermail/python-modules-team/2019-October/059368.html.

Sorry. I hadn't realised that the package tracker address was forwarding
to a mailing list. That looks good to me.

> >  I'm open to
> >closing the bug if that's the consensus _and_ everyone involved,
> >including upstream, has had an opportunity to comment.
> 
> I have posted a summary at https://github.com/python-trio/trio/issues/1#issuecomment-544304785 and asked for an upstream opinion.

Thank you for driving the discussion with upstream.

Based on their response, I wanted to update trio in Debian to the latest
upstream release and thought we could then close this bug now and allow
python-trio to migrate to testing. I have now updated Debian to trio
0.13.0 so I am now closing this bug accordingly.

> I notice that python-msrest has already been included in ubuntu eoan,
> so version 0.11.0 is going to be around for a while in at least one
> major Linux distro whatever we do now in Debian.

FWIW, Ubuntu Eoan has nine months' support only, so it's rather
different from an Ubuntu LTS in terms of longevity. Ubuntu Focal is
scheduled to release next month and will be the first major distro
release with a long term lock to this trio version (0.13.0 at the
moment).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/python-modules-team/attachments/20200223/b156cfbe/attachment.sig>