Thanks for taking the time Stefan
1. I had left in the stderr to print out the message (for whatever reason
the log files weren't there)
The two big things I'm noticing
First, I'm attempting to build with "pip install ." or "python -m pip
install ." I can confirm that the virtualenv python is us
OK I'm an idiot, and learned a bit about packaging
To debug, I ran `pip install . --no-build-isolation` it worked (using
venv's numpy)
I realized then 🤦 after visiting meson-python docs I needed to add "numpy"
as a dependency in pyproject.toml. And that pip running with build
isolation uses a dif
Hi Doug,
On Sun, Nov 26, 2023, at 06:29, Doug Turnbull wrote:
> To debug, I ran `pip install . --no-build-isolation` it worked (using venv's
> numpy)
When developing NumPy, we typically build in the existing environment. This is
done either via `pip install -e .` (which installs hooks to trigge
The next NumPy triage meeting will be held this Wednesday, November 29th at
6pm UTC (note the new time!). This is a meeting where we synchronously
triage prioritized PRs and issues.
Join us via Zoom:
https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09
.
Everyone is welco
I want to caution about using `pip install -e .` to get a development
install of numpy. This will work fine working on numpy itself, but won’t be
useful if you need to use the development version of numpy to build another
library. This doesn’t work because in-place installs don’t install the
numpy
On Sun, Nov 26, 2023, at 12:03, Nathan wrote:
> For my work I tend to use a persistent build directory with build isolation
> disabled as discussed in the meson-python docs.
Out of curiosity, how is this different from, e.g., `spin build` which builds
into `./build-install`?
Stéfan
