If you're going to require users to install their own, then there needs to be enough of a stub to TELL them that they need to install one of their own.
Since Apple provides Python3 as part of the CLT, it seems much more reasonable to trigger an install of that, vs being told to use one or the other of the competing package solutions.
If the user were to be told to "figure it out themselves", then IMO the link should be to python.org. I would resist being told, for example, to go to Homebrew to install a Python3.
On Mon, Oct 11, 2021, at 3:46 AM, John Joyce via TextMate wrote:
Definitely best to have users install their own.
On Oct 11, 2021, at 18:53, Jacob Carlborg via TextMate <textmate@lists.macromates.com> wrote:
"If an app uses Python 2.7, macOS now triggers an alert indicating that the developer must update the app to ensure it will work in future versions of macOS. (80221011)" [1]
Python will be removed or already has been removed from macOS (it’s been deprecated for a couple of release now). Looks like the command needs to be updated. I’m not sure what’s the best solution is. For the bundle itself to bundle Python or for TextMate to bundle Python in a similar way as it does with Ruby 1.8.7.
Got this error when selecting a command (that uses #!/usr/bin/python)
(under Monterey 12.1 beta)…
<Screen Shot 2021-10-09 at 12.41.46.png>
_______________________________________________
_______________________________________________
TextMate mailing list -- textmate@lists.macromates.com
To unsubscribe send an email to textmate-leave@lists.macromates.com
_______________________________________________