Have you any idea how much work is involved for not only Indigo but also all the 3rd party developers to rewrite the core of their product in Python 3 based on the whim of Apple?
Apple warned it was coming, and it was expected that it would happen in 13.0
Matt & Jay I’m sure have been working tirelessly on getting Indigo ready ahead of 13.0, usually issuing private betas to 3rd party developers once they’re somewhere close.
For Apple to suddenly pull it early, it’s impossible for a 2-man team to respond that quickly. They’ve done all they can to warn users not to upgrade; every recent Apple release going back years has had bugs that Indigo have had to respond to, and each has carried the same warnings from Jay.
You’re going to have to wait for the upgrade to be available, when and only when Matt & Jay feel it is ready for the public and they’re confident that enough developers have had sufficient time to fix their plugins.
Sent from my iPhone using Tapatalk Pro