🌐 Mailman 3 December 2014 - Pythonmac-SIG - python.org

PyObjC 3.0.1 on PyPI
by Ronald Oussoren Jan. 2, 2015

Jan. 2, 2015

Hi, I’ve just pushed PyObjC 3.0.1 to PyPI. This is a major update to the previously uploaded release and contains a rewrite of the core bridge itself. All tests pass without problems, but there could still be problems. With this update the bridge is a lot lazier about when to add methods to the class proxy __dict__: methods are now only added when they are actually used. This should result in slightly better performance, and more importantly removes some very ugly code that tried very hard to keep the __dict__ up to date without there being support for detecting changes to a class in the Objective-C runtime. Because of this it is more important that ever to have “from objc import super” at the top of modules that use super calls in subclasses of Cocoa classes. In previous releases this was already necessary to avoid a race condition, but with this release you will definitely run into problems when using builtin.super. I am working on a PEP that adds a new API to Python that would remove the need of a custom super class, but that will at best be present in Python 3.5 (and that’s assuming the PEP is accepted). The metadata and framework wrappers have not yet been updated with support of OSX 10.9, let alone support of 10.10. That means that those wrappers work fine on OSX 10.9, but any special support for API’s introduced in OSX 10.9 is not present yet. Adding such support is on my todo list, but is a significant amount of work and sadly enough requires updating some tooling I used previously (which means yet more work). Getting out this release took way to much time, I started work on this during a Dropbox hack week in Januari 2013 (!). It’s highly unlikely that this rewrite and cleanup would have happend without the uninterrupted week of hacking during that event, it what just not something I could have managed in the couple of (fragmented) hours a week I can spent on PyObjC at the moment. Ronald P.S. I’ve also done some more optimisation work with PyObjC 3.0 which has sped up method calls by removing malloc calls in a number of cases. That seems to have been more effective for speed enhancements than the core rewrite itself ;-)

2 1

Issue Building App with Py2app 0.9
by Michael Forzano Dec. 13, 2014

Dec. 13, 2014

Hello, I am attempting to build my app on OSX 10.8, the stock Python 2.7.2 and the latest Py2app (0.9 I believe). I am getting the error TypeError: dyld_find() got an unexpected keyword argument 'loader' as described in https://bitbucket.org/ronaldoussoren/py2app/issue/137/py2app-problems-using…. I made the change to the file in question changing loader to loader_path. The app builds successfully, but when I attempt to run it I get "ImportError: No Module name os". If there is no plan to fix this soon, could someone let me know which versions of these packages are known to work? It would be much appreciated as this is blocking our upcoming release. Thanks, Mike

1 1

Re: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen apps problems
by Paul Wiseman Dec. 2, 2014

Dec. 2, 2014

On 1 December 2014 at 17:08, John Lewis <jklewis(a)deathstar.org> wrote: > > Sounds like either the openssl module got corrupted or had a permission > issue. It’s calling out a specific line number, if you wanted to track down > the root problem you’d need to look there. > I don't think it's either of those. I think that hashlib.py must have changed in 2.7.9 from 2.7.8 (no longer has _hashlib.openssl_md_meth_names) so the built app (running 2.7.8) expected that attribute to be there, but somehow py2app or my usage of it is causing it to look in the system libraries over the frozen libraries. Installing 2.7.8 again hides the issue because whichever hashlib it uses would have the same behaviour because they'll be identical (both from v2.7.8) > > In any case, a fresh install seems to have solved the problem. > > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman(a)gmail.com> wrote: > > I have a frozen app installed (built on a different machine using python > 2.7.8 32/ppc) > > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started > seeing errors from the built app on startup > > the error occurred from import hashlib > > File > "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py", > line 138, in <module> > _hashlib.openssl_md_meth_names) > AttributeError: 'module' object has no attribute 'openssl_md_meth_names' > > Installing 2.7.8 again on this machine, and the frozen app started working > again with no other changes. > > Is this a problem with my setup or an issue with the freezing process? > > Paul > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG > > >

2 4

Re: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen apps problems
by Paul Wiseman Dec. 1, 2014

Dec. 1, 2014

On 1 December 2014 at 17:08, John Lewis <jklewis(a)deathstar.org> wrote: > > Sounds like either the openssl module got corrupted or had a permission > issue. It’s calling out a specific line number, if you wanted to track down > the root problem you’d need to look there. > > In any case, a fresh install seems to have solved the problem. > > Unless I'm mistaken- the frozen app should be completely unaffected and independent from my local python install- it should be using it's own internal hashlib, not the one from /Library/Frameworks folder. The frozen app was working fine, I installed 2.7.9 and the frozen app started throwing this error, then after reverting back to 2.7.8 the frozen app was working again (I should stress that the frozen app was never rebuilt and remained as-is) > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman(a)gmail.com> wrote: > > I have a frozen app installed (built on a different machine using python > 2.7.8 32/ppc) > > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started > seeing errors from the built app on startup > > the error occurred from import hashlib > > File > "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py", > line 138, in <module> > _hashlib.openssl_md_meth_names) > AttributeError: 'module' object has no attribute 'openssl_md_meth_names' > > Installing 2.7.8 again on this machine, and the frozen app started working > again with no other changes. > > Is this a problem with my setup or an issue with the freezing process? > > Paul > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG > > >

1 0

Installing python 2.7.9rc1 caused my frozen apps problems
by Paul Wiseman Dec. 1, 2014

Dec. 1, 2014

I have a frozen app installed (built on a different machine using python 2.7.8 32/ppc) I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started seeing errors from the built app on startup the error occurred from import hashlib File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py", line 138, in <module> _hashlib.openssl_md_meth_names) AttributeError: 'module' object has no attribute 'openssl_md_meth_names' Installing 2.7.8 again on this machine, and the frozen app started working again with no other changes. Is this a problem with my setup or an issue with the freezing process? Paul

1 0