While preparing our latest manuscript, I found a problem with the new M1 Macbooks running MADByTE:
They didn’t run it.
So, after some panic about what could have gone wrong, I noticed that the GUI infrastructure that MADByTE uses has a bit of a problem running on apple silicon. So, I updated the pyqt5 package and verified it ran.
Then, just a few days ago, it stopped running… again..
So, remembering this issue, I found that once again the M1 Macbooks had updated beyond what the fixed version of pyqt5 we recommend was. Once again, I updated the pyqt5 version and we’re back in business.
So, if you’re struggling to get MADByTE to launch, try updating pyqt5 first. If the problem persists, feel free to reach out to me directly and I’ll work with you to figure out what may be going wrong. We’ll try to keep the repo up to date, but if it isn’t - just let me know!