On 1 Apr, 2008, at 22:09, has wrote:
On 1 Apr 2008, at 19:03, Kevin Walzer wrote:What does the "de-Macification" in Python 3.0 mean? Will the Carbon modules be removed?I've found the answer to my own question: http://www.python.org/dev/peps/pep-3108/ Yuk. Looks like I will have to remove the Carbon bits from my app at some point!Or just do what I did with appscript: fork off the bits you need and update them yourself.
I'd prefer if we'd move the interesting bits of the Carbon bindings totheir own package(s). One of the nice things of the current Carbon bindings is that a large portion of the API is just there and you probably don't have
to write C code when you want to use an API. Sadly enough that's only true of API's that were present in OS9, but the idea stands: it would be nice to have complete bindings to the bits of Carbon that still make sense. IMHO that would exclude all GUI-related code, but I'm a bit biased ;-) Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
