From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: jupyterlab
Date: Fri, 21 May 2021 18:42:21 +0200 [thread overview]
Message-ID: <20210521164221.1d7ulKylDfK3ku1p8gymmShxJWEaHU8Eo-6r3UXg55Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30873@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/30873#issuecomment-846094493
Comment:
I force-pushed a couple of fixes and broke the check cycle by disabling checks in `python3-jupyter_core`, `python3_jupyter_client` and `python3-ipython_ipykernel`. However, there are still some changes that should be made:
1. Please take ownership of all the new packages added here. I am not interested in maintaining the ones I added to support my earlier effort, and you should also control `python3-pyrsistent` since you are adding it to support Jupyter.
2. There are still some other tests that fail and need to be reconciled. I didn't fix everything in the list.
3. Rename `python3-jupyter_nbclassic` to `python3-nbclassic`. (Most of the existing `python3-jupyter*` packages are misnamed, but I don't know if we want to bother renaming them now; we should at least pick the right name for new packages.)
4. I don't think this resolves the `jupyter console` issue I was having, which also triggers some test failures in (I think) `python3-nbformat`. This seems to be related to PyZMQ, but I haven't dug into it and am not sure if there is an upstream fix somewhere. That needs to be resolved.
next prev parent reply other threads:[~2021-05-21 16:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 16:03 [PR PATCH] [wip] new " dkwo
2021-05-14 16:06 ` dkwo
2021-05-14 16:08 ` dkwo
2021-05-14 16:28 ` FollieHiyuki
2021-05-15 11:48 ` [PR PATCH] [Updated] " dkwo
2021-05-15 12:13 ` dkwo
2021-05-15 12:18 ` New " dkwo
2021-05-15 12:30 ` ahesford
2021-05-21 16:36 ` [PR PATCH] [Updated] " ahesford
2021-05-21 16:42 ` ahesford [this message]
2021-05-22 18:25 ` dkwo
2021-05-22 18:28 ` dkwo
2021-05-22 19:01 ` dkwo
2021-05-22 21:24 ` [PR PATCH] [Updated] " dkwo
2021-05-22 21:36 ` dkwo
2021-05-22 21:50 ` dkwo
2021-05-26 18:31 ` [PR REVIEW] " non-Jedi
2021-05-27 18:53 ` dkwo
2021-05-27 19:06 ` non-Jedi
2021-05-27 19:07 ` non-Jedi
2021-06-02 8:21 ` dkwo
2021-06-02 10:25 ` ahesford
2021-06-04 17:31 ` [PR PATCH] [Updated] " dkwo
2021-06-04 17:31 ` dkwo
2021-06-04 17:35 ` [PR PATCH] [Updated] " dkwo
2021-06-05 7:56 ` dkwo
2021-06-05 7:57 ` dkwo
2021-06-05 8:24 ` [PR PATCH] [Updated] " dkwo
2021-06-05 9:21 ` dkwo
2021-06-07 13:52 ` ahesford
2021-06-07 14:14 ` [PR PATCH] [Updated] " dkwo
2021-06-07 15:23 ` ahesford
2021-06-07 17:02 ` [PR PATCH] [Updated] " dkwo
2021-06-07 17:12 ` dkwo
2021-06-07 18:13 ` dkwo
2021-06-07 19:36 ` [PR PATCH] [Closed]: " ahesford
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=20210521164221.1d7ulKylDfK3ku1p8gymmShxJWEaHU8Eo-6r3UXg55Y@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).