Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert numpy.i changes, pin swig<4.3.0 #1276

Merged
merged 2 commits into from
Nov 28, 2024
Merged

Revert numpy.i changes, pin swig<4.3.0 #1276

merged 2 commits into from
Nov 28, 2024

Conversation

mferrera
Copy link
Contributor

Resolves #1275

We can unpin swig once we drop support for Python 3.8 and move forward with #1233

This reverts commit 743b2ce.
This version and the changes to numpy.i that come with it (pulled
directly from the numpy repository) caused segfaults under certain
circumstances in Python 3.8, in particular when in a context where
pandas>2 is used. It's very difficult to understand the interactions
causing these problems and the most prudent thing to do seems to be to
wait until we deprecate support for Python 3.8 and then unpin swig.
@mferrera mferrera self-assigned this Nov 28, 2024
@mferrera mferrera requested a review from a team November 28, 2024 08:51
Copy link
Collaborator

@jcrivenaes jcrivenaes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a good solution 👍

@mferrera mferrera merged commit 839503b into main Nov 28, 2024
39 checks passed
@mferrera mferrera deleted the xtgeo-segfault-test branch November 28, 2024 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Segfault from xtgeo 4.3.2
2 participants