This is beyond my pay grade, but an automatic install is probably not going to happen, but pointing to Homebrew might be a good idea. But the PATH problem is confusing, at least to me. I still don't know what version my Ruby scripts are going to use.
Monterey not shipping with Python and Ruby may be a good thing since the version are not up to date. But
On Oct 11, 2021, at 11:43, L. Philip Schumm via TextMate textmate@lists.macromates.com wrote:
On Oct 11, 2021, at 6:10 AM, Timothy Bates via TextMate textmate@lists.macromates.com wrote:
Pretty sure a healthy chunk of us don’t want to understand these innards.
Agreed, nor should you have to just to use TM to casually edit and execute Python scripts. Anything more substantial than that, and I think you can assume that the user will know a bit about managing her or his Python installation(s).
TM installing a copy would make sense for us, with a pref to allow superusers to sim link to their privately maintained set.
The easiest way to link to a specific Python installation is in .tm_properties. But I agree, an option for an automatic install on Monterey if a Python interpreter is not found on the PATH would be nice. However, I don't think TM should manage that installation; IMHO the best option would be either initiating a standard install of the latest stable version from python.org or a homebrew install of the latest available version. That way, if the user wishes, she or he could can manage/extend the resulting install using standard tools and expectations.
-- Phil