pyobjc-dev — CVS commit notices go here

[Pyobjc-dev] PyObjC 2.2b1 won't install on a Macbook Pro

[Ron G. <ro...@fl...>]

[Apologies if this is a repeat.  First attempt seems to have failed.]

Followed the instructions and got this on a Macbook Pro (i.e. an Intel  
machine) running Python 2.6, OS X 10.5.6 and XCode 3.0:

[ron@mickey:~]$ sudo easy_install pyobjc==2.2b1
Searching for pyobjc==2.2b1
Best match: pyobjc 2.2b1
Processing pyobjc-2.2b1-py2.6.egg
pyobjc 2.2b1 is already the active version in easy-install.pth

Using /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ 
site-packages/pyobjc-2.2b1-py2.6.egg
Processing dependencies for pyobjc==2.2b1
Searching for pyobjc-framework-ScreenSaver==2.2b1
Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/
Reading http://pyobjc.sourceforge.net
Best match: pyobjc-framework-ScreenSaver 2.2b1
Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b1.tar.gz#md5 
=efc75de2224a13c1726b67307c37a99e
Processing pyobjc-framework-ScreenSaver-2.2b1.tar.gz
Running pyobjc-framework-ScreenSaver-2.2b1/setup.py -q bdist_egg -- 
dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ 
easy_install-m0V45R/pyobjc-framework-ScreenSaver-2.2b1/egg-dist-tmp- 
fWseAC
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ 
distutils/dist.py:266: UserWarning: Unknown distribution option:  
'options'
  warnings.warn(msg)
ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib,  
file is not of required architecture for architecture ppc
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU++ 
+TI/-Tmp-//ccuez0lM.out (No such file or directory)
error: Setup script exited with error: command 'gcc' failed with exit  
status 1


Clues appreciated.  Thanks.

rg

[Pyobjc-dev] Problem with animator proxy

[Jonas O. <jo...@fr...>]

Hi,

I'm having the same problem as the author of this post: 
http://news.gmane.org/gmane.comp.python.pyobjc.devel/cutoff=5048

Basically, my application crashes whenever I try to invoke 'setFrame' on 
the animator proxy. 'performSelector' works fine, but as the author of the 
original post already noted isn't of much use when you can't pass in any 
values. I tried using NSInvocation, but that crashes the application, too. 
Could this be a bug in PyObjC?

Jonas

[Pyobjc-dev] PyObjC 2.2b1 won't install on a Macbook Pro

[Ron G. <ro...@fl...>]

Followed the instructions and got this on a Macbook Pro (i.e. an Intel  
machine) running Python 2.6, OS X 10.5.6 and XCode 3.0:

[ron@mickey:~]$ sudo easy_install pyobjc==2.2b1
Searching for pyobjc==2.2b1
Best match: pyobjc 2.2b1
Processing pyobjc-2.2b1-py2.6.egg
pyobjc 2.2b1 is already the active version in easy-install.pth

Using /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ 
site-packages/pyobjc-2.2b1-py2.6.egg
Processing dependencies for pyobjc==2.2b1
Searching for pyobjc-framework-ScreenSaver==2.2b1
Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/
Reading http://pyobjc.sourceforge.net
Best match: pyobjc-framework-ScreenSaver 2.2b1
Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b1.tar.gz#md5 
=efc75de2224a13c1726b67307c37a99e
Processing pyobjc-framework-ScreenSaver-2.2b1.tar.gz
Running pyobjc-framework-ScreenSaver-2.2b1/setup.py -q bdist_egg -- 
dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ 
easy_install-m0V45R/pyobjc-framework-ScreenSaver-2.2b1/egg-dist-tmp- 
fWseAC
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ 
distutils/dist.py:266: UserWarning: Unknown distribution option:  
'options'
   warnings.warn(msg)
ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib,  
file is not of required architecture for architecture ppc
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU++ 
+TI/-Tmp-//ccuez0lM.out (No such file or directory)
error: Setup script exited with error: command 'gcc' failed with exit  
status 1


Clues appreciated.  Thanks.

rg

Re: [Pyobjc-dev] Dumb Question (Python 3.0)

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

On 15 May, 2009, at 18:25, Ilan Volow wrote:

>
> I've googled around for a little while, and I haven't found a clear,
> up-to-date answer on this.
>
> Does PyObjc work with Python 3.0 yet, or is it still a work in
> process? Would betting on Python 3.0+PyObjC working together in 10.6
> be a sure bet, or should I take the safe route and write my project
> purely in Objective-C for the time being?

PyObjC does not work with Python 3.x yet. I have looked at this, and  
this will be a signifant effort both because of changes in the Python  
extension API and because of changes in the language (such as abstract  
base classes). I want to get 2.2 out before a start working on that.

10.6 support will happen, but I can neither talk about that nor  
provide code without breaking NDA.

W.r.t. your last question: why is Python 2.6 not an option for you?   
IMHO Python 3.0 shouldn't be used for  application development, the  
python.org team is working hard on a release of Python 3.1 because  
that will fix some serious annoyances with 3.0. Even then a large  
subset of Python libraries won't support Python 3.

Ronald

>
> -- Ilan
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] PyObjC - X-Code - py2app - Dependencies ...

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

On 15 May, 2009, at 15:50, Mic Pringle wrote:

> Hi,
>
> I primarily develop using x-code on Leopard, and was wondering if you
> can set it up to include any dependencies in the built application
> bundle, in the same way you can with py2app ? If so, how ?

Not really. Adding code to py2app to do this is on my todo list, but  
that's probably not something I'll get around to soon.

Ronald

>
> Thanks
>
> -Mic
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] Dumb Question (Python 3.0)

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

I haven't seen any checkins relating to Python 3 yet, so barring any  
ultra-secret work on this (or perhaps a branch I haven't noticed), I'd  
say that Python 3 work hasn't even started yet.

That said, the safest bet is to use the current stable, released  
version of PyObjC, or even helping out with the 2.2 beta.

I'm confused about the "purely Objective-C" option. That is clearly  
the safest thing to do, but you will not gain any of the benefits  
PyObjC gives you.

With regard to 10.6, even if Ronald has done any work on it, he's  
probably under NDA and will not be able to confirm anything at this  
point.

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




On 15 May 2009, at 19:25, Ilan Volow wrote:

>
> I've googled around for a little while, and I haven't found a clear,
> up-to-date answer on this.
>
> Does PyObjc work with Python 3.0 yet, or is it still a work in
> process? Would betting on Python 3.0+PyObjC working together in 10.6
> be a sure bet, or should I take the safe route and write my project
> purely in Objective-C for the time being?
>
> -- Ilan
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] Dumb Question (Python 3.0)

[Ilan V. <li...@cl...>]

I've googled around for a little while, and I haven't found a clear,  
up-to-date answer on this.

Does PyObjc work with Python 3.0 yet, or is it still a work in  
process? Would betting on Python 3.0+PyObjC working together in 10.6  
be a sure bet, or should I take the safe route and write my project  
purely in Objective-C for the time being?

-- Ilan

[Pyobjc-dev] PyObjC - X-Code - py2app - Dependencies ...

[Mic P. <mic...@gm...>]

Hi,

I primarily develop using x-code on Leopard, and was wondering if you
can set it up to include any dependencies in the built application
bundle, in the same way you can with py2app ? If so, how ?

Thanks

-Mic

Re: [Pyobjc-dev] Problem building pyobjc from SVN

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

On 13 May, 2009, at 21:26, James Kelly wrote:

> On 4/16/09 3:36 AM, "Ronald Oussoren" <ron...@ma...> wrote:
>> Yikes, I really need to start testing with a standard build of Python
>> again. My guess is that the problem is caused by ' -isysroot /
>> Developer/SDKs/MacOSX10.4u.sdk ' in the compiler flags below. This
>> forces the compiler to use the system headers for 10.4, even when
>> building on 10.5.
>>
>> I have an idea on how to work around this (basicly force usage of -
>> isysroot=/ on OSX 10.5 or later), but won't have time to commit  
>> such a
>> change today.
>
> Hi Ronald,
>
> I'm having the same problem (except I'm attempting to use Python  
> 2.6).  I
> tried changing -isysroot to / instead of /Developer/SDKs/ 
> MacOSX10.4u.sdk,
> but while it got further it still failed to completely install  
> (failed with
> the message I'll paste below).  Any ideas?  Easy_install fails with a
> similar error.

Your problem is that you have some non-universal libraries installed  
in /usr/local, which get picked up by the compiler.  Getting the  
compiler to ignore /usr/local is annoyingly hard although I'll  
probably try to find a clean way to do that. Luckily that would only  
be needed in pyobjc core, which already has a complicated setup.py  
script.

Ronald

Re: [Pyobjc-dev] Catergory Question ...

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

On 10 May, 2009, at 19:06, Mic Pringle wrote:

> Ronald,
>
> So is there no way at all the be able to call a Python pyobj-c class
> from Obj-C as from your earlier response you did imply this ??
>
> '...the same is true for methods you add in a subclass, those can be
> called from ObjC as well...'

You can call methods on a class that's defined in Python. You cannot  
have direct references to a class that's defined in Python though.

That is:

	BKTextile* object = [BKTextile new];		// This get's you a link-time  
error
	BKTextile* object = [NSClassFromString(@"BKTextile") new] // This  
should work



>
> I'm mainly a Obj-C programmer, and have only recently turned to
> PyObj-c as a way to utilise many libraries that simply aren't
> available to Obj-C, such as for processing Textile and Yaml ?
>
> I have got it working so far using another method I found on the
> internet which involves creating a wrapper class for the Python part
> and using NSClassFromString to instantiate the class, but I was hoping
> to drop these two extra files in favour of just using a header file
> and the original Python file like with the category stuff. Is this
> then not possible ?

AFAIK the only limitation is that you cannot have [APythonClass  
classmethod] in your code, you must use NSClassFromString to access  
the class object. This is purely for technical limitations, the ObjC  
compiler needs link-time access to the class when you call a  
classmethod, and that's impossible to arrange for using PyObjC.

Ronald
>
> Thank
>
> -Mic
>
>
> 2009/5/10 Ronald Oussoren <ron...@ma...>:
>> Mic,
>>
>> You cannot refer to the class directly in Objective-C, that's  
>> because PyObjC
>> will create the class at runtime and your ObjC code tries to link  
>> to it at
>> compile-time.
>>
>> I tend to write all my code in Python, using ObjC as a way to  
>> optimize code
>> where needed and to access API's that are not available in Python.   
>> This
>> means I tend to be able to get away with creating instances in  
>> Python code,
>> while still calling methods on them in ObjC.
>>
>> Ronald
>>
>> On 10 May, 2009, at 18:26, Mic Pringle wrote:
>>
>>> Hi Ronald,
>>>
>>> As you have probably seen, I now have categories working fine,  
>>> thanks
>>> to your help.
>>>
>>> You mentioned in one of your earlier replies that I can also do the
>>> same for subclasses, not just categories. So following this I have
>>> created a header file in Objective-C with the following contents ...
>>>
>>> #import <Cocoa/Cocoa.h>
>>>
>>> @interface BKTextile : NSObject
>>>
>>> - (NSString *)decodeTextile:(NSString *)aString;
>>>
>>> @end
>>>
>>> And then created the following Python implementation ...
>>>
>>> from Foundation import *
>>> import textile
>>>
>>> class BKTextile(NSObject):
>>>
>>>        def decodeTextile_(self, aString):
>>>                return u"it worked!"
>>>
>>> Which is pretty much what I've done to get the category to work,
>>> except when I try to compile I get the following error ...
>>>
>>> .objc_class_name_BKTextile referenced from:
>>> literal-pointer@_OBJC@__cls_refs@BKTextile in PythonServerTest.o
>>> symbol(s) not found
>>>
>>> Any ideas ??
>>>
>>> Thanks,
>>>
>>> Mic
>>>
>>>
>>> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>>>
>>>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm... 
>>>> >
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Just a quick question regarding categories.
>>>>>
>>>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know  
>>>>> if I
>>>>> add a category in a PyObj-c module, will it be availble to use  
>>>>> in the
>>>>> Obj-c side of the project ??
>>>>>
>>>>> If so, does it just work or are there any special instructions I  
>>>>> need
>>>>> to follow to get it working ?
>>>>
>>>> Methods you add using an Python category are available in ObjC as  
>>>> well
>>>> (the same is true for methods you add in a subclass, those can be  
>>>> called
>>>> from ObjC as well).
>>>>
>>>> Two possible sources for confusion/problems:
>>>>
>>>> * Unless the methods you add are already known to the compiler  
>>>> you'll
>>>> have to write a header file that the ObjC compiler
>>>>  can use. You'll get compiler warnings otherwise.
>>>>
>>>> * Methods that you add in python by default have arguments and a  
>>>> return
>>>> value of type 'id'. This can be overridden by:
>>>>
>>>>  - information extracted from the superclass (if you override a  
>>>> method
>>>> PyObjC knows the new method should have the
>>>>    same signature as the one in a superclass).
>>>>  - the method is defined in an informal_protocol that's known to  
>>>> PyObjC,
>>>> the method signature is then extracted from
>>>>    that protocol
>>>>  - manual annotations (objc.accessor, objc.selector, ....)
>>>>
>>>> Ronald
>>>>>
>>>>> Thanks
>>>>>
>>>>> -Mic
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> The NEW KODAK i700 Series Scanners deliver under ANY  
>>>>> circumstances! Your
>>>>> production scanning environment may not be a perfect world - but  
>>>>> thanks
>>>>> to
>>>>> Kodak, there's a perfect scanner to get the job done! With the  
>>>>> NEW KODAK
>>>>> i700
>>>>> Series Scanner you'll get full speed at 300 dpi even with all  
>>>>> image
>>>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>>>> _______________________________________________
>>>>> Pyobjc-dev mailing list
>>>>> Pyo...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>>>
>>>>>
>>>>
>>
>>

Re: [Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Ronald,

So is there no way at all the be able to call a Python pyobj-c class
from Obj-C as from your earlier response you did imply this ??

'...the same is true for methods you add in a subclass, those can be
called from ObjC as well...'

I'm mainly a Obj-C programmer, and have only recently turned to
PyObj-c as a way to utilise many libraries that simply aren't
available to Obj-C, such as for processing Textile and Yaml ?

I have got it working so far using another method I found on the
internet which involves creating a wrapper class for the Python part
and using NSClassFromString to instantiate the class, but I was hoping
to drop these two extra files in favour of just using a header file
and the original Python file like with the category stuff. Is this
then not possible ?

Thank

-Mic


2009/5/10 Ronald Oussoren <ron...@ma...>:
> Mic,
>
> You cannot refer to the class directly in Objective-C, that's because PyObjC
> will create the class at runtime and your ObjC code tries to link to it at
> compile-time.
>
> I tend to write all my code in Python, using ObjC as a way to optimize code
> where needed and to access API's that are not available in Python.  This
> means I tend to be able to get away with creating instances in Python code,
> while still calling methods on them in ObjC.
>
> Ronald
>
> On 10 May, 2009, at 18:26, Mic Pringle wrote:
>
>> Hi Ronald,
>>
>> As you have probably seen, I now have categories working fine, thanks
>> to your help.
>>
>> You mentioned in one of your earlier replies that I can also do the
>> same for subclasses, not just categories. So following this I have
>> created a header file in Objective-C with the following contents ...
>>
>> #import <Cocoa/Cocoa.h>
>>
>> @interface BKTextile : NSObject
>>
>> - (NSString *)decodeTextile:(NSString *)aString;
>>
>> @end
>>
>> And then created the following Python implementation ...
>>
>> from Foundation import *
>> import textile
>>
>> class BKTextile(NSObject):
>>
>>        def decodeTextile_(self, aString):
>>                return u"it worked!"
>>
>> Which is pretty much what I've done to get the category to work,
>> except when I try to compile I get the following error ...
>>
>> .objc_class_name_BKTextile referenced from:
>> literal-pointer@_OBJC@__cls_refs@BKTextile in PythonServerTest.o
>> symbol(s) not found
>>
>> Any ideas ??
>>
>> Thanks,
>>
>> Mic
>>
>>
>> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>>
>>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Just a quick question regarding categories.
>>>>
>>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>>> add a category in a PyObj-c module, will it be availble to use in the
>>>> Obj-c side of the project ??
>>>>
>>>> If so, does it just work or are there any special instructions I need
>>>> to follow to get it working ?
>>>
>>> Methods you add using an Python category are available in ObjC as well
>>> (the same is true for methods you add in a subclass, those can be called
>>> from ObjC as well).
>>>
>>> Two possible sources for confusion/problems:
>>>
>>> * Unless the methods you add are already known to the compiler you'll
>>> have to write a header file that the ObjC compiler
>>>  can use. You'll get compiler warnings otherwise.
>>>
>>> * Methods that you add in python by default have arguments and a return
>>> value of type 'id'. This can be overridden by:
>>>
>>>  - information extracted from the superclass (if you override a method
>>> PyObjC knows the new method should have the
>>>    same signature as the one in a superclass).
>>>  - the method is defined in an informal_protocol that's known to PyObjC,
>>> the method signature is then extracted from
>>>    that protocol
>>>  - manual annotations (objc.accessor, objc.selector, ....)
>>>
>>> Ronald
>>>>
>>>> Thanks
>>>>
>>>> -Mic
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>>>> production scanning environment may not be a perfect world - but thanks
>>>> to
>>>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
>>>> i700
>>>> Series Scanner you'll get full speed at 300 dpi even with all image
>>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>>> _______________________________________________
>>>> Pyobjc-dev mailing list
>>>> Pyo...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>>
>>>>
>>>
>
>

Re: [Pyobjc-dev] Catergory Question ...

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

Mic,

You cannot refer to the class directly in Objective-C, that's because  
PyObjC will create the class at runtime and your ObjC code tries to  
link to it at compile-time.

I tend to write all my code in Python, using ObjC as a way to optimize  
code where needed and to access API's that are not available in  
Python.  This means I tend to be able to get away with creating  
instances in Python code, while still calling methods on them in ObjC.

Ronald

On 10 May, 2009, at 18:26, Mic Pringle wrote:

> Hi Ronald,
>
> As you have probably seen, I now have categories working fine, thanks
> to your help.
>
> You mentioned in one of your earlier replies that I can also do the
> same for subclasses, not just categories. So following this I have
> created a header file in Objective-C with the following contents ...
>
> #import <Cocoa/Cocoa.h>
>
> @interface BKTextile : NSObject
>
> - (NSString *)decodeTextile:(NSString *)aString;
>
> @end
>
> And then created the following Python implementation ...
>
> from Foundation import *
> import textile
>
> class BKTextile(NSObject):
> 	
> 	def decodeTextile_(self, aString):
> 		return u"it worked!"
>
> Which is pretty much what I've done to get the category to work,
> except when I try to compile I get the following error ...
>
> .objc_class_name_BKTextile referenced from:
> literal-pointer@_OBJC@__cls_refs@BKTextile in PythonServerTest.o
> symbol(s) not found
>
> Any ideas ??
>
> Thanks,
>
> Mic
>
>
> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>
>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm... 
>> > wrote:
>>> Hi,
>>>
>>> Just a quick question regarding categories.
>>>
>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>> add a category in a PyObj-c module, will it be availble to use in  
>>> the
>>> Obj-c side of the project ??
>>>
>>> If so, does it just work or are there any special instructions I  
>>> need
>>> to follow to get it working ?
>>
>> Methods you add using an Python category are available in ObjC as  
>> well (the same is true for methods you add in a subclass, those can  
>> be called from ObjC as well).
>>
>> Two possible sources for confusion/problems:
>>
>> * Unless the methods you add are already known to the compiler  
>> you'll have to write a header file that the ObjC compiler
>>  can use. You'll get compiler warnings otherwise.
>>
>> * Methods that you add in python by default have arguments and a  
>> return value of type 'id'. This can be overridden by:
>>
>>   - information extracted from the superclass (if you override a  
>> method PyObjC knows the new method should have the
>>     same signature as the one in a superclass).
>>   - the method is defined in an informal_protocol that's known to  
>> PyObjC, the method signature is then extracted from
>>     that protocol
>>   - manual annotations (objc.accessor, objc.selector, ....)
>>
>> Ronald
>>> Thanks
>>>
>>> -Mic
>>>
>>> ------------------------------------------------------------------------------
>>> The NEW KODAK i700 Series Scanners deliver under ANY  
>>> circumstances! Your
>>> production scanning environment may not be a perfect world - but  
>>> thanks to
>>> Kodak, there's a perfect scanner to get the job done! With the NEW  
>>> KODAK i700
>>> Series Scanner you'll get full speed at 300 dpi even with all image
>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>
>>>
>>

Re: [Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Hi Ronald,

As you have probably seen, I now have categories working fine, thanks
to your help.

You mentioned in one of your earlier replies that I can also do the
same for subclasses, not just categories. So following this I have
created a header file in Objective-C with the following contents ...

#import <Cocoa/Cocoa.h>

@interface BKTextile : NSObject

- (NSString *)decodeTextile:(NSString *)aString;

@end

And then created the following Python implementation ...

from Foundation import *
import textile

class BKTextile(NSObject):
	
	def decodeTextile_(self, aString):
		return u"it worked!"

Which is pretty much what I've done to get the category to work,
except when I try to compile I get the following error ...

.objc_class_name_BKTextile referenced from:
literal-pointer@_OBJC@__cls_refs@BKTextile in PythonServerTest.o
symbol(s) not found

Any ideas ??

Thanks,

Mic


2009/5/8 Ronald Oussoren <ron...@ma...>:
>
> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...> wrote:
>>Hi,
>>
>>Just a quick question regarding categories.
>>
>>I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>add a category in a PyObj-c module, will it be availble to use in the
>>Obj-c side of the project ??
>>
>>If so, does it just work or are there any special instructions I need
>>to follow to get it working ?
>
> Methods you add using an Python category are available in ObjC as well (the same is true for methods you add in a subclass, those can be called from ObjC as well).
>
> Two possible sources for confusion/problems:
>
> * Unless the methods you add are already known to the compiler you'll have to write a header file that the ObjC compiler
>  can use. You'll get compiler warnings otherwise.
>
> * Methods that you add in python by default have arguments and a return value of type 'id'. This can be overridden by:
>
>   - information extracted from the superclass (if you override a method PyObjC knows the new method should have the
>     same signature as the one in a superclass).
>   - the method is defined in an informal_protocol that's known to PyObjC, the method signature is then extracted from
>     that protocol
>   - manual annotations (objc.accessor, objc.selector, ....)
>
> Ronald
>>Thanks
>>
>>-Mic
>>
>>------------------------------------------------------------------------------
>>The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>>production scanning environment may not be a perfect world - but thanks to
>>Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>>Series Scanner you'll get full speed at 300 dpi even with all image
>>processing features enabled. http://p.sf.net/sfu/kodak-com
>>_______________________________________________
>>Pyobjc-dev mailing list
>>Pyo...@li...
>>https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>
>>
>

Re: [Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Thankyou all so much. Between Bob and Ronald I now have this working.

-Mic

2009/5/10 Ronald Oussoren <ron...@ma...>:
>
> On 8 May, 2009, at 13:44, Mic Pringle wrote:
>
>> Okay, fantastic !
>>
>> Would it be possible for you to give me an example of your last point
>> (re: manual annotations for some method you may use in a category) as
>> this is the only part I don't have any experience with ?
>>
>> I am looking to add two methods to NSString, one which returns a
>> string and another which returns an array.
>>
>> This would be greatly appreciated.
>
> Both strings and arrays are objects and hence no manual annotation is
> needed, something like this should work:
>
> class MyStringCategory (objc.Category(NSString)):
>     def myStringValue(self):
>          return u"hello"
>
>     def myArrayValue(self):
>          return [1,2]
>
>
> You only need manual annotations when an argument or return value is a basic
> C type (such as a C "int" or "NSPoint"). Adding annotations is described in
> the pyobjc documentation and is definitely advanced behaviour because it
> uses some very lowlevel machinery.
>
>
> Ronald
>>
>> Thanks
>>
>> -Mic
>>
>> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>>
>>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Just a quick question regarding categories.
>>>>
>>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>>> add a category in a PyObj-c module, will it be availble to use in the
>>>> Obj-c side of the project ??
>>>>
>>>> If so, does it just work or are there any special instructions I need
>>>> to follow to get it working ?
>>>
>>> Methods you add using an Python category are available in ObjC as well
>>> (the same is true for methods you add in a subclass, those can be called
>>> from ObjC as well).
>>>
>>> Two possible sources for confusion/problems:
>>>
>>> * Unless the methods you add are already known to the compiler you'll
>>> have to write a header file that the ObjC compiler
>>>  can use. You'll get compiler warnings otherwise.
>>>
>>> * Methods that you add in python by default have arguments and a return
>>> value of type 'id'. This can be overridden by:
>>>
>>>  - information extracted from the superclass (if you override a method
>>> PyObjC knows the new method should have the
>>>    same signature as the one in a superclass).
>>>  - the method is defined in an informal_protocol that's known to PyObjC,
>>> the method signature is then extracted from
>>>    that protocol
>>>  - manual annotations (objc.accessor, objc.selector, ....)
>>>
>>> Ronald
>>>>
>>>> Thanks
>>>>
>>>> -Mic
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>>>> production scanning environment may not be a perfect world - but thanks
>>>> to
>>>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
>>>> i700
>>>> Series Scanner you'll get full speed at 300 dpi even with all image
>>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>>> _______________________________________________
>>>> Pyobjc-dev mailing list
>>>> Pyo...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>>
>>>>
>>>
>
>

Re: [Pyobjc-dev] Catergory Question ...

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

On 8 May, 2009, at 13:44, Mic Pringle wrote:

> Okay, fantastic !
>
> Would it be possible for you to give me an example of your last point
> (re: manual annotations for some method you may use in a category) as
> this is the only part I don't have any experience with ?
>
> I am looking to add two methods to NSString, one which returns a
> string and another which returns an array.
>
> This would be greatly appreciated.

Both strings and arrays are objects and hence no manual annotation is  
needed, something like this should work:

class MyStringCategory (objc.Category(NSString)):
      def myStringValue(self):
           return u"hello"

      def myArrayValue(self):
           return [1,2]


You only need manual annotations when an argument or return value is a  
basic C type (such as a C "int" or "NSPoint"). Adding annotations is  
described in the pyobjc documentation and is definitely advanced  
behaviour because it uses some very lowlevel machinery.


Ronald
>
> Thanks
>
> -Mic
>
> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>
>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm... 
>> > wrote:
>>> Hi,
>>>
>>> Just a quick question regarding categories.
>>>
>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>> add a category in a PyObj-c module, will it be availble to use in  
>>> the
>>> Obj-c side of the project ??
>>>
>>> If so, does it just work or are there any special instructions I  
>>> need
>>> to follow to get it working ?
>>
>> Methods you add using an Python category are available in ObjC as  
>> well (the same is true for methods you add in a subclass, those can  
>> be called from ObjC as well).
>>
>> Two possible sources for confusion/problems:
>>
>> * Unless the methods you add are already known to the compiler  
>> you'll have to write a header file that the ObjC compiler
>>  can use. You'll get compiler warnings otherwise.
>>
>> * Methods that you add in python by default have arguments and a  
>> return value of type 'id'. This can be overridden by:
>>
>>   - information extracted from the superclass (if you override a  
>> method PyObjC knows the new method should have the
>>     same signature as the one in a superclass).
>>   - the method is defined in an informal_protocol that's known to  
>> PyObjC, the method signature is then extracted from
>>     that protocol
>>   - manual annotations (objc.accessor, objc.selector, ....)
>>
>> Ronald
>>> Thanks
>>>
>>> -Mic
>>>
>>> ------------------------------------------------------------------------------
>>> The NEW KODAK i700 Series Scanners deliver under ANY  
>>> circumstances! Your
>>> production scanning environment may not be a perfect world - but  
>>> thanks to
>>> Kodak, there's a perfect scanner to get the job done! With the NEW  
>>> KODAK i700
>>> Series Scanner you'll get full speed at 300 dpi even with all image
>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>
>>>
>>

Re: [Pyobjc-dev] Mixin classes

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

Johan Rydberg wrote:

> I suspect that this comes from the fact the the first class must
> be the Objective-C class.
> 
> With that constrain, a mixin class wouldn't be able to override
> methods of the first class.

Yes, I think that's the reason I did it the way I did.

A better idea might be to search the base classes for
one that derives from NSObject and use that as the
"main" class, then merge from right to left.

-- 
Greg

Re: [Pyobjc-dev] Mixin classes

[Johan R. <joh...@gm...>]

>> Note that this implementation results in methods in
>> later base classes overriding those in earlier ones,
>> which is more or less the opposite of what normally
>> happens. If you use this technique, you might want
>> to reverse the order of the merging.
>
> Wouldn't it be more useful to tweak NSMulticlass to do the updates of the
> class dict in the right order?

I suspect that this comes from the fact the the first class must
be the Objective-C class.

With that constrain, a mixin class wouldn't be able to override
methods of the first class.

Re: [Pyobjc-dev] Mixin classes

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

Ronald Oussoren wrote:
> 
> On 8 May, 2009, at 1:46, Greg Ewing wrote:
> 
>> If you use this technique, you might want
>> to reverse the order of the merging.
> 
> Wouldn't it be more useful to tweak NSMulticlass to do the updates of  
> the class dict in the right order?

That's what I meant by "reverse the order of the merging".

-- 
Greg

Re: [Pyobjc-dev] Catergory Question ...

[Bob V. <pyo...@bo...>]

I believe you must define stringFromTextile: as a class method in  
Python because that's how you're defining its interface in Objective-C.

Don't know what the @objc.signature('#:#:) aims to accomplish, but I  
think this should work instead:

     @classmethod
     def stringFromTextile_(self, aString):


Bob


On May 8, 2009, at 10:35 AM, Mic Pringle wrote:

> Hi Ronald,
>
> I'm still having issues with this. My category is defined in the file
> NSStringTextile.py as follows ...
>
> from Foundation import *
> import objc
> import textile
>
> class NSString(objc.Category(NSString)):
>
> 	@objc.signature('#:#')
> 	def stringFromTextile_(self, aString):
> 		try:
> 			data = textile.textile(aString)
> 		except:
> 			data = ''
> 		return data
>
> And my header file, NSStringTextile.h, as follows ...
>
> #import <Cocoa/Cocoa.h>
>
> @interface NSString (Textile)
>
> + (NSString *)stringFromTextile:(NSString *)aString;
>
> @end
>
> However, when ever I try to use the category I get the following
> message box popup ...
>
> [NSString stringFromTextile:]: unrecognized selector sent to class  
> 0xa0839f20
>
> I have also added my python file to main.py
>
> Any ideas on where I'm going wrong ?
>
> Cheers
>
> -Mic
>
> 2009/5/8 Ronald Oussoren <ron...@ma...>:
>>
>> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm... 
>> > wrote:
>>> Hi,
>>>
>>> Just a quick question regarding categories.
>>>
>>> I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>> add a category in a PyObj-c module, will it be availble to use in  
>>> the
>>> Obj-c side of the project ??
>>>
>>> If so, does it just work or are there any special instructions I  
>>> need
>>> to follow to get it working ?
>>
>> Methods you add using an Python category are available in ObjC as  
>> well (the same is true for methods you add in a subclass, those can  
>> be called from ObjC as well).
>>
>> Two possible sources for confusion/problems:
>>
>> * Unless the methods you add are already known to the compiler  
>> you'll have to write a header file that the ObjC compiler
>>  can use. You'll get compiler warnings otherwise.
>>
>> * Methods that you add in python by default have arguments and a  
>> return value of type 'id'. This can be overridden by:
>>
>>   - information extracted from the superclass (if you override a  
>> method PyObjC knows the new method should have the
>>     same signature as the one in a superclass).
>>   - the method is defined in an informal_protocol that's known to  
>> PyObjC, the method signature is then extracted from
>>     that protocol
>>   - manual annotations (objc.accessor, objc.selector, ....)
>>
>> Ronald
>>> Thanks
>>>
>>> -Mic
>>>
>>> ------------------------------------------------------------------------------
>>> The NEW KODAK i700 Series Scanners deliver under ANY  
>>> circumstances! Your
>>> production scanning environment may not be a perfect world - but  
>>> thanks to
>>> Kodak, there's a perfect scanner to get the job done! With the NEW  
>>> KODAK i700
>>> Series Scanner you'll get full speed at 300 dpi even with all image
>>> processing features enabled. http://p.sf.net/sfu/kodak-com
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!  
> Your
> production scanning environment may not be a perfect world - but  
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW  
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Hi Ronald,

I'm still having issues with this. My category is defined in the file
NSStringTextile.py as follows ...

from Foundation import *
import objc
import textile

class NSString(objc.Category(NSString)):

	@objc.signature('#:#')
	def stringFromTextile_(self, aString):
		try:
			data = textile.textile(aString)
		except:
			data = ''
		return data

And my header file, NSStringTextile.h, as follows ...

#import <Cocoa/Cocoa.h>

@interface NSString (Textile)

+ (NSString *)stringFromTextile:(NSString *)aString;

@end

However, when ever I try to use the category I get the following
message box popup ...

[NSString stringFromTextile:]: unrecognized selector sent to class 0xa0839f20

I have also added my python file to main.py

Any ideas on where I'm going wrong ?

Cheers

-Mic

2009/5/8 Ronald Oussoren <ron...@ma...>:
>
> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...> wrote:
>>Hi,
>>
>>Just a quick question regarding categories.
>>
>>I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>add a category in a PyObj-c module, will it be availble to use in the
>>Obj-c side of the project ??
>>
>>If so, does it just work or are there any special instructions I need
>>to follow to get it working ?
>
> Methods you add using an Python category are available in ObjC as well (the same is true for methods you add in a subclass, those can be called from ObjC as well).
>
> Two possible sources for confusion/problems:
>
> * Unless the methods you add are already known to the compiler you'll have to write a header file that the ObjC compiler
>  can use. You'll get compiler warnings otherwise.
>
> * Methods that you add in python by default have arguments and a return value of type 'id'. This can be overridden by:
>
>   - information extracted from the superclass (if you override a method PyObjC knows the new method should have the
>     same signature as the one in a superclass).
>   - the method is defined in an informal_protocol that's known to PyObjC, the method signature is then extracted from
>     that protocol
>   - manual annotations (objc.accessor, objc.selector, ....)
>
> Ronald
>>Thanks
>>
>>-Mic
>>
>>------------------------------------------------------------------------------
>>The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>>production scanning environment may not be a perfect world - but thanks to
>>Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>>Series Scanner you'll get full speed at 300 dpi even with all image
>>processing features enabled. http://p.sf.net/sfu/kodak-com
>>_______________________________________________
>>Pyobjc-dev mailing list
>>Pyo...@li...
>>https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>
>>
>

Re: [Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Okay, fantastic !

Would it be possible for you to give me an example of your last point
(re: manual annotations for some method you may use in a category) as
this is the only part I don't have any experience with ?

I am looking to add two methods to NSString, one which returns a
string and another which returns an array.

This would be greatly appreciated.

Thanks

-Mic

2009/5/8 Ronald Oussoren <ron...@ma...>:
>
> On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...> wrote:
>>Hi,
>>
>>Just a quick question regarding categories.
>>
>>I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>>add a category in a PyObj-c module, will it be availble to use in the
>>Obj-c side of the project ??
>>
>>If so, does it just work or are there any special instructions I need
>>to follow to get it working ?
>
> Methods you add using an Python category are available in ObjC as well (the same is true for methods you add in a subclass, those can be called from ObjC as well).
>
> Two possible sources for confusion/problems:
>
> * Unless the methods you add are already known to the compiler you'll have to write a header file that the ObjC compiler
>  can use. You'll get compiler warnings otherwise.
>
> * Methods that you add in python by default have arguments and a return value of type 'id'. This can be overridden by:
>
>   - information extracted from the superclass (if you override a method PyObjC knows the new method should have the
>     same signature as the one in a superclass).
>   - the method is defined in an informal_protocol that's known to PyObjC, the method signature is then extracted from
>     that protocol
>   - manual annotations (objc.accessor, objc.selector, ....)
>
> Ronald
>>Thanks
>>
>>-Mic
>>
>>------------------------------------------------------------------------------
>>The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>>production scanning environment may not be a perfect world - but thanks to
>>Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>>Series Scanner you'll get full speed at 300 dpi even with all image
>>processing features enabled. http://p.sf.net/sfu/kodak-com
>>_______________________________________________
>>Pyobjc-dev mailing list
>>Pyo...@li...
>>https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>
>>
>

Re: [Pyobjc-dev] Catergory Question ...

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

 
On Friday, May 08, 2009, at 10:59AM, "Mic Pringle" <mic...@gm...> wrote:
>Hi,
>
>Just a quick question regarding categories.
>
>I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
>add a category in a PyObj-c module, will it be availble to use in the
>Obj-c side of the project ??
>
>If so, does it just work or are there any special instructions I need
>to follow to get it working ?

Methods you add using an Python category are available in ObjC as well (the same is true for methods you add in a subclass, those can be called from ObjC as well).

Two possible sources for confusion/problems:

* Unless the methods you add are already known to the compiler you'll have to write a header file that the ObjC compiler
  can use. You'll get compiler warnings otherwise.

* Methods that you add in python by default have arguments and a return value of type 'id'. This can be overridden by:

   - information extracted from the superclass (if you override a method PyObjC knows the new method should have the
     same signature as the one in a superclass).
   - the method is defined in an informal_protocol that's known to PyObjC, the method signature is then extracted from
     that protocol
   - manual annotations (objc.accessor, objc.selector, ....)

Ronald
>Thanks
>
>-Mic
>
>------------------------------------------------------------------------------
>The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>production scanning environment may not be a perfect world - but thanks to
>Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>Series Scanner you'll get full speed at 300 dpi even with all image 
>processing features enabled. http://p.sf.net/sfu/kodak-com
>_______________________________________________
>Pyobjc-dev mailing list
>Pyo...@li...
>https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>
>

[Pyobjc-dev] Catergory Question ...

[Mic P. <mic...@gm...>]

Hi,

Just a quick question regarding categories.

I have a hybrid Obj-c/PyObj-c application and I'd like to know if I
add a category in a PyObj-c module, will it be availble to use in the
Obj-c side of the project ??

If so, does it just work or are there any special instructions I need
to follow to get it working ?

Thanks

-Mic

Re: [Pyobjc-dev] Mixin classes

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

On 8 May, 2009, at 1:46, Greg Ewing wrote:

> Ronald Oussoren wrote:
>
>> Mixins cannot be used to add new  methods that the ObjC runtime  
>> will see.
>
> In PyGUI I'm using the following metaclass to get a
> similar effect to multiple inheritance. It merges the
> class dicts of all the base classes before creating
> the class.
>
> Usage example:
>
> class PyGUI_NSWindow(NSWindow, PyGUI_NS_EventHandler):	
>  __metaclass__ = NSMultiClass
>  ...
>
> The first base class should be an ObjC class; the
> rest can be ordinary Python classes.
>
> Note that this implementation results in methods in
> later base classes overriding those in earlier ones,
> which is more or less the opposite of what normally
> happens. If you use this technique, you might want
> to reverse the order of the merging.

Wouldn't it be more useful to tweak NSMulticlass to do the updates of  
the class dict in the right order?

Ronald

>
> #--------------------------------------------------
>
> from inspect import getmro
>
> def NSMultiClass(name, bases, dic):
>  #  Workaround for PyObjC classes not supporting
>  #  multiple inheritance properly. Note: MRO is
>  #  right to left across the bases.
>  main = bases[0]
>  dic2 = {}

That is:
      for mix in bases[::-1]:
>  for mix in bases[1:]:
>    for cls in getmro(mix)[::-1]:
>      dic2.update(cls.__dict__)

      # drop the next line:
>  dic2.update(dic)
>  cls = type(main)(name, (main,), dic2)
>  return cls
>
> #--------------------------------------------------
>
> -- 
> Greg

Re: [Pyobjc-dev] Mixin classes

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

Ronald Oussoren wrote:

> Mixins cannot be used to add new  
> methods that the ObjC runtime will see.

In PyGUI I'm using the following metaclass to get a
similar effect to multiple inheritance. It merges the
class dicts of all the base classes before creating
the class.

Usage example:

class PyGUI_NSWindow(NSWindow, PyGUI_NS_EventHandler):	
   __metaclass__ = NSMultiClass
   ...

The first base class should be an ObjC class; the
rest can be ordinary Python classes.

Note that this implementation results in methods in
later base classes overriding those in earlier ones,
which is more or less the opposite of what normally
happens. If you use this technique, you might want
to reverse the order of the merging.

#--------------------------------------------------

from inspect import getmro

def NSMultiClass(name, bases, dic):
   #  Workaround for PyObjC classes not supporting
   #  multiple inheritance properly. Note: MRO is
   #  right to left across the bases.
   main = bases[0]
   dic2 = {}
   for mix in bases[1:]:
     for cls in getmro(mix)[::-1]:
       dic2.update(cls.__dict__)
   dic2.update(dic)
   cls = type(main)(name, (main,), dic2)
   return cls

#--------------------------------------------------

-- 
Greg