Was the py3.10 version of 2024.2.1 yanked from GitHub? It seems to be missing.
If it was yanked, should users not be using it?
Hi There,
It looks like that version is available here though you are right there is no windows version, only mac, 3.10 - I can’t recall is the windows 3.10 every existed actually - was that the version you are referring to?
Thanks,
Becca
Yeah. I have seen some evidence that it did exist:
- PsychoPy’s download page says that “PsychoPy has supported Python 3.10 since 2022.2.0”
- A discourse post here refers to it specifically
- archive.org’s backup of the github releases page shows that this version once had 6 downloadable assets, but only 5 are available now
A different and potentially superseding question: what’s the difference between 2024.2.1, 2024.2.1post4, and2024.2.4?
I don’t have notes on it but I have a feeling that something was missed in the build process (e.g. git wasn’t packaged?). Certainly when we packaged a “post” version it usually means that nothing in the code itself has changed but possibly something about the included files.
In general I would recommend using
- at least the newest version from a major release (2024.2.5 will nearly always be only better than 2024.2.1)
- probably the newest version altogether
- then use the useVersion system to fix a specific version for already-running studies
Hope that helps
Thanks, @jon - so just to confirm on these “post” versions, 2024.2.1post4 is more like 2024.2.1 than 2024.2.4?
Edit - also, while I have you - what’s the status of 2025.2.1? I saw it was published on GitHub and PyPI a couple of weeks ago, but still isn’t available on the website.
Correct, 2024.2.1post4 contains identical psychopy code to 2024.2.1 but the build/release went wrong for some reason
You mean 2025.1.0 I think? This is fairly normal. We tend to release in a staggered manner, with github+pypi first, then the “blue button” on our downloads page a couple of weeks later and an announcement on social media a week or two after that. We do that so the enthusiasts grab their copy first and we can fix any urgent bugs before the next wave of people encounter them, although this time I’m not aware of any major bugs being found
As it happens, the updated downloads page went live today showing 2025.1.0, along with a new stable/beta distinction that we’re now making more explicit.
If you still aren’t seeing 2025.1.0 there then try doing force refresh on the page (Ctrl-Shift-R ?) to get a fresh copy rather than cached copy
1 Like