[Pyobjc-dev] PyObjC 2.2b1 CoreVideo problem

[Orestis M. <or...@or...>]

Just easy_installed PyObjC 2.2b1 into a fresh virtualenv.

Other than the issue that 'from Quartz import *' that I know is fixed  
in trunk, CoreVideo seems to be broken:

 >>> from Quartz.CoreVideo import *
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/Users/orestis/Developer/virtualenvs/edm/lib/python2.5/site- 
packages/pyobjc_framework_Quartz-2.2b1-py2.5-macosx-10.5-i386.egg/ 
Quartz/CoreVideo/__init__.py", line 17, in <module>
     scan_classes=False)
   File "/Users/orestis/Developer/virtualenvs/edm/lib/python2.5/site- 
packages/pyobjc_core-2.2b1-py2.5-macosx-10.5-i386.egg/objc/ 
_bridgesupport.py", line 144, in initFrameworkWrapper
     _parseBridgeSupport(data, globals, frameworkName,  
inlineTab=inlineTab)
   File "/Users/orestis/Developer/virtualenvs/edm/lib/python2.5/site- 
packages/pyobjc_core-2.2b1-py2.5-macosx-10.5-i386.egg/objc/ 
_bridgesupport.py", line 57, in _parseBridgeSupport
     objc.parseBridgeSupport(data, globals, frameworkName, *args,  
**kwds)
objc.internal_error: PyObjCRT_SkipTypeSpec: Unhandled type '65'  
encode(CVTimeStamp*)

This also breaks QuartzCore (which imports CoreVideo), which contains  
a lot of CoreAnimation constants, and it's a showstopper for our  
adoption of PyObjC 2.2 (we'd quite like to use it, we're using the  
Leopard version currently).

Not sure if this is fixed on the trunk - didn't see anything relevant  
in the commit logs. Any documentation on building from trunk so we can  
help with bug reports? With virtualenv it's very easy to run an  
application on both 2.0 and 2.2 and report breakage.

Orestis
--
or...@or...
http://orestis.gr/