Additionally, since the site-package is installed in the .pscyopy3 directory this issue persists across reinstalls of the app.

I guess you've installed a plugin that had numpy>=2 as a requirement so that's been installed here. Any idea what packages/plugins you had installed that led to this? Hopefully our recommended packages don't have that

I mean, I guess we need to work out what the right solution is here if a user installs something that clashes with core psychopy (and systems like pdm that check detailed requirements constraints are a minefield!)

Additionally, since the site-package is installed in the .pscyopy3 directory this issue persists across reinstalls of the app.

That aspect is certainly by design

• we think most users would want their plugins (and dependencies of those) to be use
• we can't install inside the app itself because that would mean the user changing the app for all other users (and would require admin permissions)

It was moviepy that I installed. For the webcam component.

I totally understand that design decision. It’s just that once I borked the system it took some wrangling to recover. Uninstalling moviepy from within didn’t remove numpy. Just wanted to identify that it’s a failure mode that bricks across installs.

Numpy 2 is really annoying at the moment because of the incompatibility and ease that installs upgrade things and the lack of specific protection for numpy<2.0 having not yet proliferated.