4 ms·
That’s true if they’re using it from the command-line, but not if they’re using apps that linked against the system SDK’s libpython2.7.dylib (and assumed PyObjC
by mrpippy 5y ago
That’s true if they’re using it from the command-line, but not if they’re using apps that linked against the system SDK’s libpython2.7.dylib (and assumed PyObjC would be present)
- TillE 5y agoIs there any significant software still using that? Apple is pretty aggressive about breaking backwards compatibility, as they did with x86, so it's no real surprise for unmaintained software to become completely unusable.
- Wowfunhappy 5y agoNotably, however, Apple didn't drop x86 support in a minor update.
- mrpippy 5y agoAnd kept the support present for I think a year and a half alongside a runtime warning message (and removed SDK support earlier than that)
- mrpippy 5y agoBased on what they’ve done, I guess the answer is no. My company was shipping (somewhat niche) software linking with the built-in python2 up until last year though, and it’s been a scramble since Monterey to rebuild things to avoid the warning message. Definitely thought we would have python2 until 13.0 though (and part of me wonders whether this is just a “brown-out” for the beta and 12.3 release will be back to normal)