From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Jupyter updates
Date: Mon, 27 Nov 2023 12:56:49 +0100 [thread overview]
Message-ID: <20231127115649.IaSTFNHjyeqrBzdUNKOS2KICF82UNZp2_z4Gy5sH_Ts@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]
There's a merged pull request on the void-packages repository
Jupyter updates
https://github.com/void-linux/void-packages/pull/47424
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Summary:
- python3-openapi-core: update to 0.18.2.
- python3-rpds-py: update to 0.13.1.
- python3-referencing: update to 0.31.0.
- python3-jsonschema-specifications: update to 2023.11.1.
- python3-jsonschema: update to 4.20.0.
- python3-jsonschema-path: update to 0.3.2.
- python3-fastjsonschema: update to 2.19.0.
- python3-comm: update to 0.2.0.
- python3-jupyter_client: update to 8.6.0.
- python3-ipython_ipykernel: update to 6.27.0.
- python3-jupyter_ipywidgets: depend on widgetsnbextension.
- python3-jupyter_events: update to 0.9.0.
- python3-jupyterlab_pygments: update to 0.3.0.
- python3-nbclient: update to 0.9.0.
- python3-jupyter_nbconvert: update to 7.11.0.
- python3-jupyter_qtconsole: update to 5.5.1.
- python3-jupyter_server: update to 2.11.0.
- python3-jupyterlab_server: update to 2.25.2.
- jupyterlab: update to 4.0.9.
I think qtconsole 5.4 was the last dependent of `python3-ipython_genutils` so that pkg could in principle be removed.
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-11-27 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 2:44 [PR PATCH] " tornaria
2023-11-27 11:56 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231127115649.IaSTFNHjyeqrBzdUNKOS2KICF82UNZp2_z4Gy5sH_Ts@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).