From: airplanemath <airplanemath@aol.com>
To: cygwin@cygwin.com
Subject: Re: python-numpy (1.22.0-1) can't be imported
Date: Thu, 13 Jan 2022 21:04:06 -0500 [thread overview]
Message-ID: <vriu8rvj13ah.fsf@mail.aol.com> (raw)
In-Reply-To: <b13535c2-c2fd-ff98-9777-f42b62eced8f@gmail.com>
On Wed, Jan 12 2022, Marco Atzeri wrote:
> On 12.01.2022 12:47, ggl329 wrote:
>> Hi Marco,
>> I upgraded python39-numpy to 1.22.0-1, and failed to import numpy.
>> It seems that mtrand.cpython-39-x86_64-cygwin.dll does not have
>> PyInit_mtrand.
>> Could you check if numpy can be imported in your environment?
>>
>
> working on it.
> In theory I have not changed the build between the two versions
> but there was a patch in 1.19.4-1 for similar issue.
>
> Regards
> Marco
I have the same problems with the distribution NumPy package, but I can
use a locally-compiled NumPy with no patches. It doesn't look like your
build has any patches either:
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpython-numpy-src%2Fpython-numpy-1.22.0-1-src&grep=numpy
so that's fun.
Out of curiousity, what options are you passing for cpu-baseline and
cpu-dispatch?
https://numpy.org/devdocs/reference/simd/build-options.html
I don't see the newest cygport in the Cygwin package repository.
next prev parent reply other threads:[~2022-01-14 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:47 ggl329
2022-01-12 22:16 ` Marco Atzeri
2022-01-14 2:04 ` airplanemath [this message]
2022-01-18 20:55 ` Marco Atzeri
2022-01-22 1:04 ` Masamichi Hosoda
2022-01-22 5:24 ` Marco Atzeri
2022-01-22 10:16 ` Masamichi Hosoda
2022-01-23 9:42 ` Masamichi Hosoda
2022-02-06 17:35 ` airplanemath
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=vriu8rvj13ah.fsf@mail.aol.com \
--to=airplanemath@aol.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).