public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: airplanemath <airplanemath@aol.com>
To: cygwin@cygwin.com
Subject: Re: python-numpy (1.22.0-1) can't be imported
Date: Sun, 06 Feb 2022 12:35:36 -0500	[thread overview]
Message-ID: <vriuh79bq4nr.fsf@mail.aol.com> (raw)
In-Reply-To: <20220122.191639.929494193658372882.trueroad@trueroad.jp>

On Sat, Jan 22 2022, Masamichi Hosoda wrote:

>> It is something like that, but "-Wl,--export-all-symbols"
>> is not used on 1.21.4 and is not needed for most of the other
>> modules on 1.22.x
>> 
>> so I am looking for a less extreme action.
>> Also to understand how it can impact other python subpackages
>
> If I understand correctly, I've found the root cause of the issue.
> I've sent a pull request to numpy.
> https://github.com/numpy/numpy/pull/20874

Based on that pull request, it looks like it's related to the patches
used to avoid python C-extension modules with only one exported function
mentioned a year ago:
https://cygwin.com/pipermail/cygwin/2021-January/247211.html
https://cygwin.com/pipermail/cygwin/2021-January/247216.html
From a glance at the Python C API docs, it looks like Python C extension
modules are supposed to have only one exported function:
https://docs.python.org/3/extending/extending.html#the-module-s-method-table-and-initialization-function
https://docs.python.org/3/extending/extending.html#providing-a-c-api-for-an-extension-module

The NumPy CFFI tests seem to want to use a few C extension modules as
normal shared libraries, which requires that the functions the tests
want to use to be exported from the DLL, but this seems to be a somewhat
unusual case.

I tend to compile my own versions of Cython (without patches), which may
have been picked up when I compiled the new version of NumPy.


      parent reply	other threads:[~2022-02-06 17:35 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
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 [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=vriuh79bq4nr.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).