I was wondering if there are good resources about migrating a typedesign-developer environment safely from python 2.7 to python 3.
I (finally) read the Notarisation Tutorial by @yanone (Thank you so much for compiling that) , but I am still generally scared by Catalina and that wicked extra effort.
Here’s what made me stand in my corner to shame:
If you’re still working with Python 2 they might not work (the
subprocess
part) and then I have to tell you that I don’t care and that there’s no help for you and that it’s 2019 and that you need to urgently go into a corner of shame and think about your life.
Well, here’s the thing:
I got literally thousands of .py files, and perhaps 90% of em are to be used in the type design workflow.
How’s it possible to migrate all of them to python 3? I cannot go through all of them and make the changes manually. Batch processing sounds rather scary, you never know what you break along with it.
What’s the safest way to get the actual Mac OS python properly set up to python 3. My Mac came with 2.7 and I often heard that it’s better to not mess with the the system python. But now I need to. How can one keep the dev environment working and migrate the system to python 3?
I am asking here, because this is rather specifically bound to GlyphsApp python integration, its API and an environment that was cast around GlyphsApp since years and years.
Thanks so much for any little twig of help.
On an unrelated side note:
I’m afraid that Apple causes the potential dead of many free plugins on the long run. With forcing to pay for a developer account and imprinting lots of extra work on the developers for each and every little plugin, the motivation to give work away for free gets minimised a lot. But that’s of course not your cup of tea