Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python3-ipython: update to 8.14.0.
Date: Mon, 05 Jun 2023 19:35:18 +0200	[thread overview]
Message-ID: <20230605173518.gJUoYUJdRH0l6lPlnkjtNcnb4WoeGDIC2PNL1ZfH92k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44268@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

There's a closed pull request on the void-packages repository

python3-ipython: update to 8.14.0.
https://github.com/void-linux/void-packages/pull/44268

Description:
 - switch to pep517 build style: needs using a venv
 - update depends and checkdepends
 - break unnecessary checkdepends cycle with ipython_ipykernel

#### Testing the changes
- I tested the changes in this PR: **briefly**

I will run sagemath testsuite with this update and report back.

@ahesford here's one package where testing with `PYTHONPATH` breaks and testing in a venv works. I wrote a custom `do_check()` function but you'll see it's quite generic and could be moved to `build-style/python3-pep517.sh`.

Maybe you can figure out a different way to make the generic testing with `PYTHONPATH` to work.

<!--
#### 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
-->


      parent reply	other threads:[~2023-06-05 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 21:07 [PR PATCH] " tornaria
2023-06-04 21:27 ` tornaria
2023-06-04 21:34 ` [PR PATCH] [Updated] " tornaria
2023-06-05  1:19 ` tornaria
2023-06-05  1:42 ` tornaria
2023-06-05  6:20 ` [PR REVIEW] " tornaria
2023-06-05 15:05 ` ahesford
2023-06-05 15:05 ` ahesford
2023-06-05 15:05 ` ahesford
2023-06-05 17:03 ` tornaria
2023-06-05 17:05 ` [PR PATCH] [Updated] " tornaria
2023-06-05 17:07 ` [PR REVIEW] " ahesford
2023-06-05 17:35 ` 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=20230605173518.gJUoYUJdRH0l6lPlnkjtNcnb4WoeGDIC2PNL1ZfH92k@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).