Open tungol opened 6 months ago
hmm. i'm on m2 and m3 macs and never had this issue. i'll investigate.
If you can't replicate the issue let me know and I'll see if I can find more specific conditions
i just faced this problem while working on https://github.com/vigo/textmate2-ruff-linter. none of the textmate's cocoa related dialogs, nibs are competible. also, ruby versions are incompetible with cpu. but still, did not get any python package releated issue. is it possible to record a small video that i see whats going on? i also upgraded this bundle and will do small improvements which i implemented in my ruff linter
I'll try to get that video. If it's been a while and I haven't gotten that to you, that means I probably just forgot and you're welcome to ping me about it.
By default, pip installs a compiled version of black appropriate for the current architecture. On an ARM Macbook, that ends up with an error message like this:
The main problem being that we're using the ancient ruby18 bundled with Textmate, which is x86 only. If we allow Python FMT to use system ruby instead, this happens:
The problem here is that the provided
Bundle Support.tmbundle/Support/shared/lib/textmate.rb
importsBundle Support.tmbundle/Support/shared/lib/osx/plist.bundle
, which is a compiled ruby extension, distributed by Textmate as a binary for x86_64, i386, and ppc_7400 (!).Possible solutions to this:
shared/lib/textmate.rb
which comments out the plist import (possibly breaking any plist-parsing ruby-based bundles that happily run in ruby18 with x86-mode?)TextMate::Process.run()
entirely. In this case, maybetextmate2-python-fmt
could package a version of the necessary functions which avoids importing plist.bundle