[Numpy-discussion] Re: Future of numpy.distutils
Hi Evgeni,
Thanks for your input, apparently, you project uses `meson-pep517`
while scipy uses `meson-python` for interfacing meson with the python
side of the building.
For now, I am not settled on one version or another but among the
python community there should be one and only one obvious way to do
things ...
Meson does its job properly, the binary extensions are properly
compiled, but neither on my code, nor on scipy, those shared library
are shipped within the wheel.
There are several warnings like this (and many more when building scipy):
WARNING Using heuristics to map files to wheel, this may result in incorrect
locations
WARNING File could not be mapped to an equivalent wheel directory:
/tmp/build-via-sdist-jsg87qg9/fabio-0.15.0-a0/.mesonpy-5bwmoite/install/usr/lib/python3/dist-packages/fabio/ext/cf_io.cpython-39-x86_64-linux-gnu.so
({moduledir_shared}/cf_io.cpython-39-x86_64-linux-gnu.so)
Is this bug fixed is any "unreleased" version of `meson-python` which
would explain this works for some people but not for me ?
The simplest is probably to open a bug there.
Cheers,
Jerome
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Future of numpy.distutils
On Mon, Jun 13, 2022 at 11:52 AM Jerome Kieffer
wrote:
> Hi Evgeni,
>
> Thanks for your input, apparently, you project uses `meson-pep517`
> while scipy uses `meson-python` for interfacing meson with the python
> side of the building.
>
> For now, I am not settled on one version or another but among the
> python community there should be one and only one obvious way to do
> things ...
>
I think meson-python is going to be better maintained, it's moving a lot
faster. Which is not a coincidence, since Filipe (the main author) reports
to me and is getting significant day job time for working on meson-python.
For SciPy we are going with meson-python.
That said, I agree that we'd like to consolidate both projects and ideally
maintain them under the Meson GitHub organization.
> Meson does its job properly, the binary extensions are properly
> compiled, but neither on my code, nor on scipy, those shared library
> are shipped within the wheel.
> There are several warnings like this (and many more when building scipy):
>
> WARNING Using heuristics to map files to wheel, this may result in
> incorrect locations
> WARNING File could not be mapped to an equivalent wheel directory:
> /tmp/build-via-sdist-jsg87qg9/fabio-0.15.0-a0/.mesonpy-5bwmoite/install/usr/lib/python3/dist-packages/fabio/ext/
> cf_io.cpython-39-x86_64-linux-gnu.so ({moduledir_shared}/
> cf_io.cpython-39-x86_64-linux-gnu.so)
>
> Is this bug fixed is any "unreleased" version of `meson-python` which
> would explain this works for some people but not for me ?
> The simplest is probably to open a bug there.
>
I answered on https://github.com/FFY00/meson-python/issues/80. This should
be fixed soon (it's a blocker for SciPy too).
Cheers,
Ralf
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Future of numpy.distutils
Hi Jerome,
Yeah, don't read too much into my choice of the pep517 wrapper ---
IIRC I just did "monkey see, monkey do" on
https://github.com/FRidh/mesonpep517examples, it worked for my simple
and limited use case and that was it. Last time I checked though,
mesonpep517 did not work on Windows (it might have been fixed already,
will check at some point). So this depends on your needs I guess.
Evgeni
On Mon, Jun 13, 2022 at 12:53 PM Jerome Kieffer wrote:
>
> Hi Evgeni,
>
> Thanks for your input, apparently, you project uses `meson-pep517`
> while scipy uses `meson-python` for interfacing meson with the python
> side of the building.
>
> For now, I am not settled on one version or another but among the
> python community there should be one and only one obvious way to do
> things ...
>
> Meson does its job properly, the binary extensions are properly
> compiled, but neither on my code, nor on scipy, those shared library
> are shipped within the wheel.
> There are several warnings like this (and many more when building scipy):
>
> WARNING Using heuristics to map files to wheel, this may result in incorrect
> locations
> WARNING File could not be mapped to an equivalent wheel directory:
> /tmp/build-via-sdist-jsg87qg9/fabio-0.15.0-a0/.mesonpy-5bwmoite/install/usr/lib/python3/dist-packages/fabio/ext/cf_io.cpython-39-x86_64-linux-gnu.so
> ({moduledir_shared}/cf_io.cpython-39-x86_64-linux-gnu.so)
>
> Is this bug fixed is any "unreleased" version of `meson-python` which
> would explain this works for some people but not for me ?
> The simplest is probably to open a bug there.
>
> Cheers,
>
> Jerome
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: evgeny.burovs...@gmail.com
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
