Path: csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod From: Mattia Rizzolo Newsgroups: linux.debian.maint.python Subject: Re: Numpy migration? Date: Sun, 06 Jan 2019 19:00:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jan 6 17:58:45 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CNfT9TXqV7nd4cfk" Content-Disposition: inline X-Info: Keep It Simple, Stupid. X-Operating-System: Linux, kernel 4.19.0-1-amd64, inside Debian GNU/Linux buster/sid sid. X-Message-Flag: WARNING!! Outlook sucks. A lot. User-Agent: Every email client sucks, this one just sucks less. X-Mailing-List: archive/latest/16664 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190106175829.GH23578@mapreri.org Approved: robomod@news.nic.it Lines: 62 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 6 Jan 2019 18:58:30 +0100 X-Original-Message-ID: <20190106175829.GH23578@mapreri.org> X-Original-References: <87a7kfqk65.fsf@orrococo> <8736q7qh9w.fsf@orrococo> <20190105153545.GB26988@mapreri.org> <87tvimq4vf.fsf@orrococo> <20190105221009.GA23578@mapreri.org> <87h8elpy5u.fsf@orrococo> Xref: csiph.com linux.debian.maint.python:11213 --CNfT9TXqV7nd4cfk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 06, 2019 at 05:07:41PM +0100, Ole Streicher wrote: > Now it turns out that there is a new migration problem, which is aplpy: > Current aplpy (2.0~rc2-2) CI test works well You probably mean aplpy 1.1.1-4. > - with numpy-1.15.4-2 (testing) and matplotlib-2.2.2-4 (testing), > - with numpy-1.16.0~rc2-1 (unstable) and matplotlib-3.0.2-2 (unstable). >=20 > However it does not work well when combining numpy-1.16.0~rc2 (unstable) > and matplotlib-2.2.2-4 (testing), which is the combination that is > tested for migration of numpy. Needless to say that matplotlib migrates > only after numpy. What should one do here? Declaring another > "Breaks: matplotlib (<< 3.0)" in numpy? Well, to me it seems it's python3-astropy that is missing a dependency on python3-skimage there, to be honest: |> from skimage.measure import block_reduce |E ModuleNotFoundError: No module named 'skimage' | |/usr/lib/python3/dist-packages/astropy/nddata/utils.py:370: ModuleNotFound= Error However I wouldn't be able to tell you why it would pass with numpy and matplotlib from unstable, given that neither pulls in skimage=E2=80=A6 --=20 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=3Dmattia `- --CNfT9TXqV7nd4cfk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlwyQcIACgkQCBa54Yx2 K63VPRAAsljIePzJrMo7FrJIruM2QF+tlCWYXN3uh7s9OxYcYT6z8tvvXt8MnQoy 3+haGFMY4gKR6757ejmevd7YOlsXmLA74gGzqe6GzXLxL+elKHjBy12hozK7H+QK n6cHztsyywkdh3+7w1PO3lV94quASlQW7ZgKlJkkvc0uSyv6eH9cSvUbJ2sBr396 4Rql6reSmJhzTvx9LZTZhrMJnfJ0FQ2MmZnkVi06l7nT7JYPQ2YijyTXvRTfycgo DXCJ3f6Z17IwnAGxJGTgIIx64Jz3Wp1+EeJ8xStOgV0PsZJJrFyRxW1HW07uZTBP iOabT3N8D3Yi5idU9YoQzUpcCXltHv+dT13AK5YFA4tp1pEs6GNApf3Wtgf7/f98 lD40etSRbsWZHPNVbR1VCOpppkAaTzYdP41Ne+/rhk9IQ/4u5jhHuP0ajtBKHau+ lAQjhkB2g1/LVOnEDGmcOWlG1592gLGBAC+pu162v5goX+kqcguMlKCnJXfG6zel 41OWerh9NedRyUCuLUZvMf3g6rKHCf78ZJeXtBxcsdat8e/Cn5VW3OFZ8+IMdC1N dE30S/LMXjp5QXLojlQf4yHErxeXx1gJDGoMOz1xnTEAWpI+NAaSOGj8797p3MK6 J8bK47ivA6SJwbj+KPrLXXt64ZN3hL4JmLYVnrz/oHgW1IbLgyo= =a3A6 -----END PGP SIGNATURE----- --CNfT9TXqV7nd4cfk--