pyobjc-dev

[Pyobjc-dev] PyObjC status for Python 3.x

[Ronald O. <ron...@ma...>]

Hi,

This is a quick status-update for the Py3k support in PyObjC: pyobjc-core and the framework wrappers can be build with Python 3.2 and most tests pass. I haven't looked at py2app yet, that probably requires some work to get it to work propertly, although with some luck it will work as is.

I'm not entirely happy yet though,   the Python-compatible interface for NSDictionary and other collection classes don't conform to the interface of the corresponding python types yet (that is, "anNSDictionary.keys()" is not a view object but returns a list just as in Python 2.x).   My plan to fix this is to first write unittests for this and then implement the required support code.

PyObjC also don't do anything with the Abstract Base Class machinery yet (see <http://docs.python.org/py3k/library/abc.html>). I plan to add that later on, both by registering Cocoa subclasses with the ABCs and by looking at the ABCs to see how a class should be proxied.

BTW. A side-effect of the py3k port is that the version of pyobjc in the repository requires python 2.6 because I use byte literals ( b"hello") to tweak the output from the 2to3 tool. I have no plans to reintroduce support for python 2.5, especially because I'd like to make some changes to the bridge that will require python 2.6. 

Ronald

Re: [Pyobjc-dev] PyObjC status for Python 3.x

[Greg E. <gre...@ca...>]

Ronald Oussoren wrote:
> BTW. A side-effect of the py3k port is that the version of pyobjc in the repository requires python 2.6 because I use byte literals ( b"hello") to tweak the output from the 2to3 tool. I have no plans to reintroduce support for python 2.5, especially because I'd like to make some changes to the bridge that will require python 2.6. 

This is a nuisance. Maybe we need a 2to2 tool which undoes all
the hacks people have to put in to get their code to work with
2to3. :-(

-- 
Greg

Re: [Pyobjc-dev] PyObjC status for Python 3.x

[Ronald O. <ron...@ma...>]

On 6 Apr, 2010, at 1:31, Greg Ewing wrote:

> Ronald Oussoren wrote:
>> BTW. A side-effect of the py3k port is that the version of pyobjc in the repository requires python 2.6 because I use byte literals ( b"hello") to tweak the output from the 2to3 tool. I have no plans to reintroduce support for python 2.5, especially because I'd like to make some changes to the bridge that will require python 2.6. 
> 
> This is a nuisance. Maybe we need a 2to2 tool which undoes all
> the hacks people have to put in to get their code to work with
> 2to3. :-(

It should be fairly easy to use something like b("bytestring") and have that work on both 3.x and 2.x, but I don't care to spend time on doing that.

The main reason I don't want to spent time on that is that I have, not fully fleshed out, plans to rewrite the machinery that determines which methods an ObjC class has. That machinery currently eagerly scans ObjC classes when they are first accessed and I want to switch to a scheme where the bridge scans classes much more lazily. That will require python 2.6 to ensure that introspection from Python still works (that is, using "dir(someObject)" to check which methods it has).  The reason for that is that python 2.6 has hooks too interact with dir(), python2.5 doesn't have that.

Ronald
> 
> -- 
> Greg
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev