Groups > linux.debian.maint.python > #14093

Updating jupyter-core to 4.10.0

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	julien.puydt@gmail.com
Newsgroups	linux.debian.maint.python
Subject	Updating jupyter-core to 4.10.0
Date	Thu, 05 May 2022 10:00:01 +0200
Message-ID	<EjEyZ-dlJ1-9@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-python-request@lists.debian.org Thu May 5 07:51:38 2022
Old-Return-Path	<julien.puydt@gmail.com>
X-Amavis-Spam-Status	No, score=-6.572 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, SARE_MSGID_LONG40=0.637, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5.5
X-Gm-Message-State	AOAM532VsaRBVT07EORJgfHKcNlEj2v0xPNYvOfUU1Gx0yLFKhhileoi BHgmGeAZ7fgeLK5KddwX9lPNYKT03vo=
X-Google-SMTP-Source	ABdhPJw8uJZVlTB0EaKWP+SqBOy8AeNdZkMIwMVVRB/xR9dyK1lJJSLI4nGqx0uBCzLMXkZvjDBeqw==
X-Received	by 2002:a05:600c:3647:b0:393:fb6b:e778 with SMTP id y7-20020a05600c364700b00393fb6be778mr3339776wmq.71.1651737083470; Thu, 05 May 2022 00:51:23 -0700 (PDT)
Content-Type	text/plain; charset="UTF-8"
Content-Transfer-Encoding	quoted-printable
User-Agent	Evolution 3.44.1-2
MIME-Version	1.0
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/19918
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/ada8b747e54971b96961b06f414514ac70609ae8.camel@gmail.com
Approved	robomod@news.nic.it
Lines	20
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 05 May 2022 09:51:28 +0200
X-Original-Message-ID	<ada8b747e54971b96961b06f414514ac70609ae8.camel@gmail.com>
Xref	csiph.com linux.debian.maint.python:14093

Show key headers only | View raw

Hi,

I tried to update jupyter-core to 4.10.0, but didn't manage to run the
upstream test suite reliably.

I first disabled it, so the package was building with both dpkg-
buildpackage and sbuild. A bad solution.

Then I re-enabled it ; it passes with dpkg-buildpackage (there's a
catch, see [1]), but not with sbuild, and I couldn't find out why.

If someone has a clue, I'm ready to learn new tricks...

J.Puydt

[1] if python3-pytest-asyncio is installed on your system, you have to
add asyncio_mode = "auto" to the relevant section of pyproject.toml,
otherwise it breaks: pytest autoloads its asyncio plugin, which doesn't
find this settings, hence warns about it, and a warning is an error ;
see: https://github.com/pytest-dev/pytest-asyncio/issues/293

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Updating jupyter-core to 4.10.0 julien.puydt@gmail.com - 2022-05-05 10:00 +0200
  Re: Updating jupyter-core to 4.10.0 Julian Gilbey <julian@d-and-j.net> - 2022-05-05 10:50 +0200
    Re: Updating jupyter-core to 4.10.0 julien.puydt@gmail.com - 2022-05-05 23:10 +0200
      Re: Updating jupyter-core to 4.10.0 Julian Gilbey <julian@d-and-j.net> - 2022-05-06 09:10 +0200

csiph-web