On 2018-04-24 07:45:16 +0200 (+0200), Matthias Klose wrote:
[...]
> Sure we can remove mercurial and OpenStack if they are not ready
> for Python3, but I'd like to avoid that. It doesn't mean that we
> should any old, upstream unmaintained Python2 dependent package.

To be clear, OpenStack has been thoroughly testing its upstream
releases against Python 3 for a while. The reason it was brought up
earlier in this thread is because Thomas has recently dropped Python
2.7 builds for it and switched to only building Python 3.x packages.
-- 
Jeremy Stanley

Attachment: signature.asc
Description: PGP signature

Reply via email to