From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: primecount: update to 7.8.
Date: Tue, 28 Mar 2023 17:30:22 +0200 [thread overview]
Message-ID: <20230328153022.jjAgnDYRQWgh4TyN4Do3DNT4PFWMprw999Aygl-RadU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43040@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]
There's a merged pull request on the void-packages repository
primecount: update to 7.8.
https://github.com/void-linux/void-packages/pull/43040
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
This is a very minor update to fix the following:
```
$ python -c 'from primecountpy.primecount import prime_pi ; print(prime_pi(-1))'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "primecountpy/primecount.pyx", line 25, in primecountpy.primecount.prime_pi
File "primecountpy/primecount.pyx", line 47, in primecountpy.primecount.prime_pi
cysignals.signals.SignalError: Bus error
```
After the update
```
$ python -c 'from primecountpy.primecount import prime_pi ; print(prime_pi(-1))'
0
```
We can now sleep in the comfort that such an important calculation can be done in void linux with success.
As expected, other values of `π(x)` are still ok and quick:
```
$ python -c 'from primecountpy.primecount import prime_pi ; print(prime_pi(1_000_000_000_000))'
37607912018
$ python -c 'from primecountpy.primecount import prime_pi ; print(prime_pi(1_000_000_000_000_000))'
29844570422669
```
<!--
#### 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-03-28 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 23:14 [PR PATCH] primecount: update to 7.7 tornaria
2023-03-27 22:28 ` classabbyamp
2023-03-28 13:34 ` [PR PATCH] [Updated] " tornaria
2023-03-28 14:41 ` primecount: update to 7.8 tornaria
2023-03-28 15:30 ` classabbyamp [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=20230328153022.jjAgnDYRQWgh4TyN4Do3DNT4PFWMprw999Aygl-RadU@z \
--to=classabbyamp@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).