Hi,

I’m slowly working my way through the SDK headers for macOS 10.12 during idle 
time at EuroPython2016, from the frameworks with small diffs to those with 
larger diffs.  

There are at the moment about 26 frameworks I haven’t looked at at all, and 
another 10 where I know I have to do some more work. The rest should have up to 
date metadata on my machine, but haven’t been tested on macOS 10.12 yet (and 
that won’t change until I get around to actually installing a VM running 10.12).

All of this was done using the headers in the Xcode 8 beta 2, I haven’t looked 
at the incremental changes to the SDK in beta 3 yet (and likely won’t until I 
have made a pass through all frameworks).  That said, the diffs from beta 2 to 
later beta’s and the final release should be fairly small (he wrote hopefully).

What needs to be done to get proper support for 10.12:

* Finish updating the metadata.  I suspect that this is a couple of days work, 
I have worked may way through the diffs of a fairly large number of frameworks, 
but haven’t looked at the more complicated ones yet (such as Foundation and 
AppKit). Also, a fairly large subset of the frameworks I have looked at didn’t 
have any significant updates compared to 10.11 (but some of them still had 
large textual diffs due to restructuring of header files).

* Install a 10.12 VM and run tests there. This will likely result in more work, 
there’s already a pull request about NSSecureCoder warnings on 10.12 that needs 
looking into and there’s bound to be more issues.

* Do the build and test dance on older OSX releases. 
   The annoying bit for that: there’s a know issue with building on OSX 10.7, 
see issue #100. I haven’t been able to look into that yet
   because I don’t have an VM with 10.7 on my laptop and haven’t been able to 
install 10.7 there yet. I probably have such a VM on
   an external disk somewhere, but I’m not sure about that.

When all that is done I can do a release that includes 10.12 support, with some 
luck around the time of the 10.12 release itself. I’ll definitely push the 
metadata updates to bitbucket once I’ve finished looking through the 10.12 SDK 
diffs.

In the longer run I want to provide wheels for PyObjC, but that requires more 
work. In particular, I only want to do that after automating more of the 
release work because I’ve noticed that I’m already postponing doing new 
releases due to the amount of work and don’t want to make things worse in that 
regard.

BTW. I’ll likely won’t work on metadata updates during the EP2016 sprints, my 
current plan is to keep the tradition of working on PEP 447 alive and try to 
actually get it accepted this year. 

Ronald

PS. “A couple of days work” probably means that it will take me several 
calendar weeks to actually finish the work because I have limited time to work 
on this and don’t want to spent all that time on this rather tedious work.

[#100]: 
https://bitbucket.org/ronaldoussoren/pyobjc/issues/100/cannot-find-interface-declaration-for
_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
https://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG

Reply via email to