From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-numpy: update to 1.25.0.
Date: Tue, 20 Jun 2023 23:18:56 +0200 [thread overview]
Message-ID: <20230620211856.akpgXk94J2xAm4syHrytqdGX--_KLPqSbOTo_K0Xpnc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44529@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/44529#issuecomment-1599570276
Comment:
Actually, this seems like a bug in musl libm:
```
$ cat cacosh.c
#include <complex.h>
#include <stdio.h>
void main()
{
double complex z = -1 -I, c;
c = cacosh(z);
printf("cacosh(z) = %6.3f %6.3f*i\n", creal(c), cimag(c));
}
$ cc cacosh.c -o cacosh -lm && ./cacosh
cacosh(z) = -1.061 2.237*i
```
Note that `cacosh(3p)` says:
```
RETURN VALUE
These functions shall return the complex arc hyperbolic cosine value,
in the range of a half-strip of non-negative values along the real axis
and in the interval [-iπ, +iπ] along the imaginary axis.
```
For whatever reason `cmath.acosh` is not catching this error (probably because it's not using C99 complex trig functions but reimplementing them from C89 real functions).
next prev parent reply other threads:[~2023-06-20 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 2:34 [PR PATCH] " tornaria
2023-06-20 2:39 ` [PR REVIEW] " ahesford
2023-06-20 2:40 ` tornaria
2023-06-20 3:02 ` tornaria
2023-06-20 20:46 ` tornaria
2023-06-20 21:18 ` tornaria [this message]
2023-06-20 21:24 ` tornaria
2023-06-21 2:46 ` ahesford
2023-06-22 21:13 ` [PR PATCH] [Updated] " tornaria
2023-06-22 21:22 ` tornaria
2023-06-25 0:04 ` tornaria
2023-06-26 2:47 ` [PR PATCH] [Updated] " tornaria
2023-06-26 3:19 ` tornaria
2023-06-26 16:04 ` [PR PATCH] [Merged]: " 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=20230620211856.akpgXk94J2xAm4syHrytqdGX--_KLPqSbOTo_K0Xpnc@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).