Skip to content

Conversation

@dham
Copy link
Member

@dham dham commented Nov 3, 2025

This was causing namespace leakage into the main firedrake namespace.

fixes #4696.

@connorjward
Copy link
Contributor

Shouldn't this go into release?

@dham
Copy link
Member Author

dham commented Nov 3, 2025

Shouldn't this go into release?

Good question. Technically it's an API change and someone's code might depend on Firedrake exposing np.

@connorjward
Copy link
Contributor

Shouldn't this go into release?

Good question. Technically it's an API change and someone's code might depend on Firedrake exposing np.

Fair enough. Sometimes it's hard to decide exactly where the line is.

@connorjward
Copy link
Contributor

This appears to be causing a lot of failures. It's not just np that is accidentally getting exported I think.

@leo-collins
Copy link
Contributor

The files inside firedrake/external_operators are also missing __all__

@sghelichkhani
Copy link
Contributor

sghelichkhani commented Nov 3, 2025

Good question. Technically it's an API change and someone's code might depend on Firedrake exposing np.

This will break our demo rendering on gadopt exactly for this reason.

But it's something we needed to fix on our side anyways. So happy with whatever happens.

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.

BUG (I guess???!!): import numpy as np leaked by firedrake.

5 participants