Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11124 > unrolled thread

Re: Upcoming pytest-4 problems

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Upcoming pytest-4 problems Mattia Rizzolo <mattia@debian.org> - 2018-11-25 14:40 +0100
    Bug#914592: [Python-modules-team] Bug#914592: Upcoming pytest-4 problems Ondrej Novy <novy@ondrej.org> - 2018-11-26 21:40 +0100
      Bug#914592: [Python-modules-team] Bug#914592: Upcoming pytest-4 problems Ondrej Novy <novy@ondrej.org> - 2018-11-27 09:40 +0100

#11124 — Re: Upcoming pytest-4 problems

[Multipart message — attachments visible in raw view] — view raw

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  `-

[toc] | [next] | [standalone]

#11127 — Bug#914592: [Python-modules-team] Bug#914592: Upcoming pytest-4 problems

[Multipart message — attachments visible in raw view] — view raw

Hi,

my plan is:

   - keep 3.x for Buster
   - upgrade to >= 4.x just after Buster release

Because we are going to drop Python after Buster release, I think it's
perfectly fine that Astropy (Py2 version) will not support Pytest 4.x.

-- 
Best regards
 Ondřej Nový

Email: novy@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

[toc] | [prev] | [next] | [standalone]

#11128 — Bug#914592: [Python-modules-team] Bug#914592: Upcoming pytest-4 problems

[Multipart message — attachments visible in raw view] — view raw

Hi,

út 27. 11. 2018 v 8:46 odesílatel Ole Streicher <olebole@debian.org> napsal:

> Thanks, however it turns out that this will unfortunately not work for
> me: from astropys POV, pytest seems to be broken in versions 3.7 - 3.10;
> see
>
> https://github.com/astropy/astropy/issues/8177


according to linked issue, that bug is fixed in 3.10.1, which is in Debian
unstable now.


> I also observed diverse failures on other (astropy dependent) packages
> with 3.10. Which basically means that I need to switch off the tests,
> unless pytests upstream provides a bugfixed 3.X version.
>

maybe just disable some of that tests? Not whole testsuite?

-- 
Best regards
 Ondřej Nový

Email: novy@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web