Package Details: psychopy 2020.1.3-4

Git Clone URL: (read-only, click to copy)
Package Base: psychopy
Description: An experiment builder for neuroscience, psychology and psychophysics
Upstream URL:
Keywords: experiment experiment-control experimental-design linguistics neuroscience psycholinguistics psychology psychophysics psychopy python science
Licenses: GPL3
Submitter: daniel_shub
Maintainer: daniel_shub
Last Packager: daniel_shub
Votes: 5
Popularity: 0.82
First Submitted: 2015-08-20 20:24
Last Updated: 2020-07-22 13:55

Latest Comments

1 2 3 Next › Last »

igord commented on 2020-10-17 19:17

@daniel_shub Thanks. Yup, removing from requires files does the job. BTW, I looked at the PsychoPy code. opencv is used as cv2 import for MovieStim2 only. Since cv2 is provided by opencv package it should work fine (haven't tested as I don't have any experiment that use movie2 simuli). So, I guess just patching setup.cfg to remove opencv-python during build should do the trick.

daniel_shub commented on 2020-10-17 17:51

@igord thanks. Not sure how I missed that. I am not sure if the problem is in this package or the opencv package. An easy work around is to simply remove the opencv-python line from the requires.txt file. I have asked what the best way forward is (

NB, you also need to install the python-certifi package which appears to be a missing dependency of matplotlib (

igord commented on 2020-10-17 10:57

Hi. I have trouble running this package. It builds fine, but it seems that it requires python-opencv in order to run. I get this when trying to run:

    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'opencv-python' distribution was not found and is required by PsychoPy

And indeed PsychoPy do require opencv-python:

~ grep opencv /usr/lib/python3.8/site-packages/PsychoPy-2020.1.3-py3.8.egg-info/requires.txt 

bassam commented on 2020-04-30 16:49

@daniel_shub I had tried to install psychopy using pip a long while ago and was unsuccessful so that might be why psychopy was in that directory. I uninstalled it using pip and the package manager. Rebooted, made sure there were no traces left, and installed it via the package manager and it's starting up fine. I'm getting a different error now when I try to run an experiment but I'll post this problem on the discourse forums. Thanks for you help.

daniel_shub commented on 2020-04-30 14:16

@bassam It looks like psychopy is running from and calling a version of python installed in /home/bassam/.local/. Unless you did something tricky, that is not the packaged version. It looks like there is some issue with gitlab and not being authorized. I do not know if this is because you installed it in .local, there is something broken in your install, or if there is something about your configuration. Regardless, I do not think it is this package that is causing the problem.

bassam commented on 2020-04-30 13:53

@daniel_shub I do get an audio warning but the same warning is there in the windows log.

1.3025  WARNING     We strongly recommend you activate the PTB sound engine in PsychoPy prefs as the preferred audio engine. Its timing is vastly superior. Your prefs are currently set to use ['sounddevice', 'PTB', 'pyo', 'pygame'] (in that order).

There seem to be other errors present however. The full log:

Unfortunately I'm a novice linux user so I'll need to look into how to create an Arch chroot first.

daniel_shub commented on 2020-04-30 13:19

@bassam I get those messages also, but psychopy works fine for me. Is there anything relevant in the .psychopy3/last_app_load.log? I wonder if it is related to the port audio changes or maybe the X11 setup. I do not have a way to test the package on Manjaro. Can you create a clean Arch chroot and try it in that container?

bassam commented on 2020-04-30 10:47

My psychopy stopped starting a couple of days ago, so I uninstalled/reinstalled it from the package manager in Manjaro. When I type psychopy in terminal the welcome screen almost becomes fully visible, then it disappears and I'm back at the terminal. This is what shows up in the terminal:

06:30:54 AM: Debug: Adding duplicate image handler for 'Windows bitmap file'
06:30:54 AM: Debug: Adding duplicate image handler for 'Windows bitmap file'
06:30:54 AM: Debug: Adding duplicate image handler for 'Windows bitmap file'

Also want to add that I never got it to actually run an experiment file in linux but things are working fine in Windows 10.

Anyway to fix this?

daniel_shub commented on 2020-04-23 02:21

@TheGoliath It now builds in a clean chroot. I deleted the "packaging" directory. I am not sure that is the right thing to do, but the resulting package passes most of the package tests with pytest==4.0.

TheGoliath commented on 2020-04-19 09:11

Traceback (most recent call last): File "", line 14, in <module> from setuptools import setup, find_packages File "/usr/lib/python3.8/site-packages/setuptools/", line 17, in <module> import setuptools.version File "/usr/lib/python3.8/site-packages/setuptools/", line 1, in <module> import pkg_resources File "/usr/lib/python3.8/site-packages/pkg_resources/", line 82, in <module> import('packaging.version') ModuleNotFoundError: No module named 'packaging.version'