[Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

[Ronald Oussoren]

> On 25 Oct 2016, at 10:36, Andrew Jaffe <a.h.jaffe at gmail.com> wrote:
> 
> On 12/10/2016 21:02, Ronald Oussoren wrote:
> >
> >> On 12 Oct 2016, at 21:09, Glyph Lefkowitz <glyph at twistedmatrix.com
> >> <mailto:glyph at twistedmatrix.com>> wrote:
> >>
> >>> On Oct 12, 2016, at 11:49 AM, Andrew Jaffe <a.h.jaffe at gmail.com
> >>> <mailto:a.h.jaffe at gmail.com>> wrote:
> >>>
> >>> Not me. If I understand correctly, Glyph -- who undoubtedly
> >>> understand the situation better than I do -- still thinks that
> >>> there's no actual bug here, since we shouldn't be using the framework
> >>> build this way, but I'm not sure I understand/agree...
> >>
> >> To be honest, I'm not 100% sure this is a good idea either; it's just
> >> that I know Donald Stufft has had a terrible time with Apple system
> >> python for several years, and he regards this as a positive change.
> >>  From my personal perspective, there's a good case to be made that a
> >> python in /System should just load from /System and one in /Library
> >> should load only from /Library, similar to the way --prefix works on
> >> "regular" UNIX.  But, this is what we've got :).
> >
> > I don’t mind if the /System python looks in /Library for stuff that the
> > user installed there, but I do consider it a bug that Apple installs
> > system files in /Library because that affects all installations of
> > Python 2.7.
> >
> > That’s what we get for playing nice with OSX conventions for where to
> > locate files :-(. Luckily this isn’t a problem for Python3 as Apple
> > doesn’t ship that (and I’d be surprised if they ever unless they start
> > shipping Python3 code as part of the OS).
> 
> Well, I did submit a radar, and although I'm not sure how far the NDA extends, I hope I can say that, unfortunately, I got a "behaves as intended" response…

That’s too bad. But I wouldn’t expect this to change anytime soon even if this would have been classified as a bug.

Ronald