On 24-jun-2005, at 12:22, Bob Ippolito wrote: >> >> Someone with copious free time should build new Carbon wrappers, we >> can than ask if the existing wrappers can be dropped in a future >> version of Python. Sadly enough that probably is with python 2.6 at >> the earliest, which is a long way away. >> > > The problem with Carbon wrappers is that they have such diminishing > returns. The longer you wait, the less reason there is to use > Carbon in the first place. > > If we just sit on our hands for another few years, all of the > functionality in Carbon will be available elsewhere anyway :)
I have no intention whatsoever to work on new Carbon wrappers because all functionality I need is already available elsewhere. However, we do need a plan to get rid of the current wrappers (especially the Carbon.CF ones) to make room for better ones. I do want to add wrappers for CoreFoundation (and frameworks based on CoreFoundation) to PyObjC and would like to drop for Carbon.CF when that's done. There may be other frameworks that are useful (OSA stuff, QuickTime) and could use wrappers with betters tests and documentation. Ronald _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
