[Pyobjc-dev] PyObjC 3.0.4 released
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2014-12-07 23:33:47
|
Hi, I just uploaded PyObjC 3.0.4 to PyPI. It contains a number of bug fixes relative to 3.0.3: * Fix installation on OSX 10.10 when using "pip install pyobjc". Issues #102, #103. * Fix crash when ``sys.modules`` contains an object that is not a string. Issue #95. * Fix crash on OSX 10.8 or later when using a 32-bit build and accessing an instance of "Object" (that is, pre-Nextstep classes). * Fix a crash when using blocks without metadata, but with a block signature from the block runtime. Issue #106 * ``PyObjCTools.MachSignals`` likely hasn't worked at all since PyObjC 2.0 because it uses a C module that was never ported to PyObjC 2.0. This private module is reintroduced in this release (with a slightly changed API) Issue #109 WARNING: Most of these fixes have not been merged to the default branch yet. That branch is still in flux due to work on supporting new API’s introduced in OSX 10.10 (and for a large part 10.9). I don’t know when the next release from the default branch (that is, 3.1) will be, that depends on how much time I can spend on updating the metadata. I expect that I can spend at best two evenings a week on this, which means I should be lucky to release 3.1 this year :-(. I’d love to spend more time on PyObjC (for example to add support for asyncio as introduced in Python 3.4), but don’t know how to arrange for that. Ronald P.S. I had hoped to release 3.0.4 last weekend, but the fix for #106 took much more time time than expected due to running into some very strange behavior that may turn out to be a system or CPython bug. |