Open aaronjnewman opened 1 year ago
Hello, thanks for the report!
It's become increasingly difficult for me to maintain and test this feedstock -- psychopy's dependencies are just so complex! For example, we don't even include the psychtoolbox package for high-precision keyboard and sound device operations. I'd been considering to pull this package off of conda-forge altogether... what's the specific reason you're using the conda-forge package over the one that can be installed via pip? :)
cc @kastman
I hear ya. And I suspect if this is the first mention of the issue that the number of people trying to use this approach is very small.
I was using this approach really just because I'm in the habit of working with conda/mamba environments generally. But it's not essential. And indeed my solution to this issue was to move psychopy down into the - pip:
section of the environment file, and then it built and ran fine.
Thanks for your feedback, @aaronjnewman, and I'm glad that using the pip
-based installation is working for you.
I'd agree. If it's hard to maintain a dedicated conda package then let's drop it. It's worse to have something available but broken than not to have it at all.
Solution to issue cannot be found in the documentation.
Issue
mamba env create -f psychopy.yml
mamba activate psychopy
Is there any reason not to update this feedstock to the current version of PsychoPy?
Installed packages
Environment info