Skip to content

Conversation

@oursland
Copy link
Collaborator

Currently numpy>=2 have issues when installed from conda-forge. Furthermore, VFX Platform currently standardizes on numpy==1.26.

This PR pins numpy to 1.26 which should resolve the current issues plaguing recent releases and ensuring compatibility with other VFX Platform compliant systems.

@oursland oursland requested a review from adrianinsaval July 15, 2025 05:09
@oursland
Copy link
Collaborator Author

Addresses #375.

@hyarion
Copy link

hyarion commented Jul 15, 2025

Should we document why we pin to these versions or how do we update them safely in the future?

@oursland
Copy link
Collaborator Author

Perhaps, but it seems to be a combination of using the latest releases of some (i.e. occt), the LTS of others (i.e. Qt), and VFX Platform, with a sprinkling of upstream compatible builds which may not be the most current.

Things like sticking to Python 3.11 was initially to keep some addons compatible with Blender. Blender is now aligned with VFX Platform, and thus we now have an actual reference we can refer to other than "we don't want to break some addons with 3rd party dependencies."

@oursland oursland merged commit 8350f8a into FreeCAD:main Jul 21, 2025
5 checks passed
@oursland
Copy link
Collaborator Author

I've merged this to get it in before the next weekly build. I'll test it after the build completes to see if it addresses the issues experienced by macros and workbenches that depend upon numpy.

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.

2 participants