Replies: 1 comment 2 replies
-
Hmm, that's hard to answer without any errors. The one thing I can see is that based on line numbers of |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've run into a problem when running a python meson build project. It's one of those cases in which it used to work, but no longer does, so I suspect its something to do with change in versions of some unpinned dependencies.
In my code, using the python build package, if I do:
everything works ok. But if I do
python3 build .
then the build looks the same, no errors, but the library built doesn't perform the same as the 'no-isolation' build, and worse, can throw segfaults.
I thought it might have been due to the introduction of numpy 2, so in my
pyproject.toml
I have:to try to match to the same version of python as in the non-isolated build, but the problem persists. I looked at the logs for both the isolated and non-isolated builds, but I couldn't see anything that stood out.
Can anybody suggest what to do to isolate the effect, and suggest a fix for this? I'd prefer to use build isolation if possible.
Here's a diff of the logs:
Beta Was this translation helpful? Give feedback.
All reactions