From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] [WIP] updates to jupyter, jupyterlab, notebook, etc.
Date: Wed, 31 May 2023 02:10:23 +0200 [thread overview]
Message-ID: <20230531001023.YJDYMMDpWkWGiaymFuEARZcoBzBbadapZfXzd0scBj8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44160@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/44160#issuecomment-1569306393
Comment:
> Thanks a lot, I'll look into this. The `ci-skip` for the circular deps is a good idea, as well as using `pip3 check` for missing deps
That's nice, the relevant ones I get are:
```
ipykernel 6.23.1 requires debugpy, which is not installed.
jupyterlab 4.0.0 requires jupyter-lsp, which is not installed.
ipywidgets 8.0.6 requires jupyterlab-widgets, which is not installed.
```
I'll look into packaging those three (also jupyterlab released 4.0.1).
BTW, I didn't mention it in the comments: I'm packaging notebook-7.0.0b3. Since 7.0.0 will be released soon, this makes sense and 6.5.4 doesn't work properly with current jupyter_client so it could be difficult supporting notebook-6.5.4 together with jupyterlab 4.0.0 for little gain...
next prev parent reply other threads:[~2023-05-31 0:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 2:01 [PR PATCH] " tornaria
2023-05-30 2:15 ` tornaria
2023-05-30 21:51 ` dkwo
2023-05-31 0:10 ` tornaria [this message]
2023-06-28 21:30 ` dkwo
2023-07-06 1:43 ` dkwo
2023-07-06 2:08 ` [PR REVIEW] " classabbyamp
2023-08-19 8:42 ` dkwo
2023-08-19 8:42 ` dkwo
2023-08-19 19:00 ` tornaria
2023-09-26 1:47 ` [PR PATCH] [Updated] " tornaria
2023-09-26 13:54 ` tornaria
2023-09-26 19:46 ` tornaria
2023-09-26 20:27 ` tornaria
2023-09-27 13:00 ` tornaria
2023-09-28 1:40 ` tornaria
2023-09-28 23:40 ` tornaria
2023-09-29 0:48 ` tornaria
2023-09-29 12:30 ` tornaria
2023-09-30 2:53 ` tornaria
2023-09-30 15:49 ` tornaria
2023-10-02 19:06 ` dkwo
2023-10-03 0:15 ` tornaria
2023-10-03 15:19 ` dkwo
2023-10-09 21:10 ` [PR PATCH] [Updated] " tornaria
2023-10-09 21:31 ` tornaria
2023-10-09 21:31 ` tornaria
2023-10-09 21:41 ` [PR PATCH] [Updated] " tornaria
2023-10-09 22:11 ` tornaria
2023-10-09 22:31 ` dkwo
2023-10-10 13:44 ` tornaria
2023-10-10 14:21 ` [PR PATCH] [Updated] " tornaria
2023-10-10 15:19 ` tornaria
2023-10-10 16:22 ` Updates " tornaria
2023-10-10 16:24 ` tornaria
2023-10-10 16:29 ` [PR PATCH] [Merged]: " ahesford
2023-10-10 17:34 ` dkwo
2023-10-10 20:32 ` tornaria
2023-10-10 21:00 ` dkwo
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=20230531001023.YJDYMMDpWkWGiaymFuEARZcoBzBbadapZfXzd0scBj8@z \
--to=tornaria@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).