You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@nickzoic what exactly is needed to enable this? Do we need a different testing setup or is it just something that needs to be configured better within Actions?
OK so I went on a bit of a mission to see if this was supportable.
Github Actions now support windows-11-arm and macos-latest test runners.
However neither of these seem happy to build Scipy / Numpy so we'd have to carefully pick versions which have wheels for those. And those versions would have to be compatible with Python 3.10 to maintain support for that.
However:
Numpy is only used for the python and score plugins
Scipy is only used for the score plugin, and then only for curve fitting
The Python plugin is not currently in use.
The Scoring plugin is using curve_fit for linear interpolation which doesn't need the might of scipy.
Perhaps it would be a good idea to back those out to avoid any binary wheels in the core countess install?
Activity
afrubin commentedon Mar 12, 2026
@nickzoic what exactly is needed to enable this? Do we need a different testing setup or is it just something that needs to be configured better within Actions?
nickzoic commentedon Mar 18, 2026
OK so I went on a bit of a mission to see if this was supportable.
Github Actions now support
windows-11-armandmacos-latesttest runners.However neither of these seem happy to build Scipy / Numpy so we'd have to carefully pick versions which have wheels for those. And those versions would have to be compatible with Python 3.10 to maintain support for that.
However:
The Python plugin is not currently in use.
The Scoring plugin is using curve_fit for linear interpolation which doesn't need the might of scipy.
Perhaps it would be a good idea to back those out to avoid any binary wheels in the core countess install?