On Sun, Nov 25, 2018 at 02:08:52PM +0100, Ole Streicher wrote:
> Pytest 4 is however the upcoming version, and I could imagine that
> others may have similar problems with Python 2 legacy. Therefore, my
> question is how these problems should be solved:
>
> * creating a legacy version package for pytest
This means yet another split.
It feels to me that too many packages are going this route.
> * remove the tests for these packages
>
> * remove the legacy packages in question completely
I'd follow these two options. For now, disable the tests when pytest 4
will land in Debian, and be ready to remove the legacy packages as a
whole soon.
After all, we are going to remove python2 itself in the upcoming years,
it doesn't really feel worth of anybody's time to work on yet other
splits, especially in cases like this where you are "only" talking about
tests for legacy and deprecated versions.
> For us, the third option would basically mean to remove the whole Python
> 2 astronomy ecosystem, and we would need to hurry in making some general
> packages Python 3 compatible (mainly astrometry.net).
I recommend you urge that ecosystem to migrate their codebases.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature