🌐 Mailman 3 March 2005 - Pythonmac-SIG - python.org

Reading Finder Labels on Folders
by Caleb Land March 22, 2005

March 22, 2005

Hello, I'm writing a backup rsync script in python (who hasn't?), but I want to be able to specify directories and files to exclude in the backup based on the file/folder's label color in the finder. I don't know anything about Carbon but I managed to scrape together code to read the label color of files: def getFileLabel(path): filespec = Carbon.File.FSSpec(path) if not os.path.isdir(path): finfo = filespec.FSpGetFInfo() else: finfo = filespec.FSpGetFInfo() return labels[getLabelNumber(finfo.Flags)] The problem is that this doesn't work on directories. Is there a way I can read the label on folders from python? Thanks. By the way, if anybody wants my script when I'm done with it just mail me and I'll send you a copy. -- Caleb Land (RedHatDude(a)gmail.com)

1 0

OT cvs version with OS-X 10.3?
by Chris Barker March 22, 2005

March 22, 2005

Hi all, Sorry for the OT question, but this is the only list I'm on with knowledgeable (about OS-X) and helpful folks. I just noticed that the cvs client I have on my box (which came with Apple's XCode tools) is version 1.10, which is pretty old, and lacks at least one feature I want (update -C). Has Apple provided and updated version? if so, how do I get it. If not, should I build from source, or use darwinports or something? thanks, -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker(a)noaa.gov

2 1

ANN: pygame 1.7.0 for Mac OS X 10.3
by Bob Ippolito March 21, 2005

March 21, 2005

Although the official sdist tarball isn't cut yet, I've packaged what should be pygame 1.7.0 for Mac OS X 10.3 users. It is available from pythonmac.org packages at: http://pythonmac.org/packages/ This installer ships with: pygame: Installed to /Library/Python2.3/ pygame headers: Installed to /System/Library/Frameworks/Python.framework/Versions/2.3/include/ python2.3/ pygame examples and documentation: Installed to /Developer/Python/pygame/ SDL with my AltiVec patches, SDL_mixer, SDL_ttf, SDL_image, smpeg: Installed to /Library/Frameworks/ To use pygame, you will need PyObjC 1.2 or later, and you will probably want Numeric and PyOpenGL installed. A PyOpenGL installer is not available from pythonmac.org packages at this time, but everything else listed is. The following improvements are especially relevant to Mac OS X: - Calls into nasty private Apple API to grab GUI access if it doesn't already have it (read: no pythonw required) - Can now read the default font and icon out of any "get_data" compliant loader (read: py2app 0.1.8 can put pygame entirely in the site-packages.zip, and it works!). - Includes newer versions of all dependencies (it sure has been a long time since 1.6.0!) - Most surface operations should be significantly faster on G4 and G5 computers due to my AltiVec patches to SDL As it has been quite a long time since the last release, there are pages full of bug fixes and feature enhancements. When the pygame.org site updates for the 1.7 release, check WhatsNew. Note that I will not be making a Mac OS X 10.2 compatible release for Python 2.3. When Python 2.4.1 is out (and probably not until there is an official distribution of it), I may build a pygame release for that. -bob

5 9

Python at WWDC
by Dave Opstad March 21, 2005

March 21, 2005

There's going to be a presentation at this year's WWDC on Python! The session topics were just released, and I noticed this one on Python: ----------------------------------------------------------------------- PyObjC is a bridge between Python and Objective-C. It allows you to write Python scripts that use and extend existing Objective-C class libraries, and most importantly, Cocoa libraries. Specific topics from the 1.2 release covered in this session are: py2app, macho_standalone, NSBundle features, KVO/KVC support, the new scanframework script, objc.inject(), and runtime editing. ----------------------------------------------------------------------- Just FYI... Dave

1 0

ETA on MacPython 2.4?
by Daniel Keep March 20, 2005

March 20, 2005

Hi all. Please be gentle--I use a PC. I'm doing my third-year computer science project at university, and we're in the early stages of requirements testing. That said, I'm also trying to extol the virtues of Python upon the group, as I honestly believe it will be the best language for our project. But there's always a fly in the ointment: most of us are using PCs (I run Windows+coLinux, and another member has Windows+BSD), but one member uses Mac OSX. As a result, cross-platform compatibility is a big issue for our program. Obviously, Python is great in this respect, but we wanted to use Python 2.4. This is mainly because I happen to really like generator expressions and decorators <g>. Anyway, I was wondering if anyone knew in even a vague sense when MacPython 2.4.1 will be released. I understand that Jack is waiting on the PythonLabs 2.4.1 release, but even having a reasonably stable preview release to work with in the meantime would be good. Will 2.4.1 be out within the next few months, or should we start looking at 2.3 instead? Thanks for your time and patience with a heathen PC user. -- Daniel -- v2sw5+8Yhw5ln4+5pr6OFPma8u6+7Lw4Tm6+7l6+7D i28a2Xs3MSr2e4/6+7t4TNSMb6HTOp5en5g6RAHCP http://hackerkey.com/

2 2

Another odd question re breaks/returns
by Michael Dunn March 20, 2005

March 20, 2005

I have a double-nested 'for' loop in a function. I can't use 'break' to get out of BOTH loops from the inner loop. Can I simply put a 'return' statement in the inner loop, or will this completely mess up the stack or something? thanks! Michael

2 1

mod_python / lib compatibility question
by Jim Muller March 20, 2005

March 20, 2005

Hi, A question from a new mod_python user: When I run within an otherwise working apache2/mod_python, if my script imports MySQLdb I get a dyld compability version error: File "/Users/jim/Sites/WatchEvents.py", line 97, in ? import MySQLdb, pickle File "/opt/local/lib/python2.4/site-packages/MySQLdb/__init__.py", line 27, in ? import _mysql ImportError: Failure linking new module: /opt/local/lib/libssl.0.9.7.dylib: dyld: /opt/local/apache2/bin/httpd version mismatch for library: /opt/local/lib/libssl.0.9.7.dylib (compatibility version of user: 0.9.7 greater than library's version: 0.9.0) Now, /opt/local/lib/libssl.0.9.7, like /opt/local/apache2/bin/httpd, and the installed copy of _mysql.so report having "(compatibility version 0.9.0, current version 0.9.7)". [Perhaps it matters that /usr/local/lib/libssl.0.9.7 has "(compatibility version 0.9.7, current version 0.9.7)", but I don't see where it's used] As I understand it [from man ld] this sort of dyld error should only occur when the program compatibility version is > the lib version -- yet the lib is version 0.9.7, >= all the compatibility versions in play. Can anyone see what I'm missing? I should point out that MySQLdb was installed in the usual way using setup.py, and I did redo this after fully updating the darwinports tree and rebuilding apache2. Apache2, mod_python, and python24 all come from darwinports. MySQLdb is of course installed, as is MySQL from Server Logistics. [Perhaps the MySQL version is the problem? Because the MySQL is not from darwinports, I had to hack the MySQLdb setup.py file to get it to use the darwinports version of libssl and thus have exactly the same compatibility version. Should I have hacked something more?] This is on lhe latest MacOS X 10.3.8. All these components work fine if I don't import MySQLdb, and MySQLdb works fine in the python interpreter. If anyone has any suggestions I'd greatly appreciate them. And BTW I'd be happy to link statically if that's doable/better/easier. Jim PS: according to locate (after running locate.update) the only libssl are: /Applications/Firefox.app/Contents/MacOS/libssl3.dylib /Applications/Navigator.app/Contents/MacOS/libssl3.dylib /opt/local/lib/libssl.0.9.7.dylib /opt/local/lib/libssl.0.dylib /opt/local/lib/libssl.a /opt/local/lib/libssl.dylib /opt/local/var/db/dports/software/openssl/0.9.7e_0/opt/local/lib/ libssl.0.9.7.dylib /opt/local/var/db/dports/software/openssl/0.9.7e_0/opt/local/lib/ libssl.0.dylib /opt/local/var/db/dports/software/openssl/0.9.7e_0/opt/local/lib/ libssl.a /opt/local/var/db/dports/software/openssl/0.9.7e_0/opt/local/lib/ libssl.dylib /usr/lib/libssl.0.9.7.dylib /usr/lib/libssl.0.9.dylib /usr/lib/libssl.dylib /usr/libexec/gdb/symfiles/libssl.0.9.7.dylib.syms /usr/libexec/gdb/symfiles/libssl.0.9.dylib.syms /usr/libexec/httpd/libssl.so -- Jim

2 1

Re: [Pythonmac-SIG] Python for OSX programming beginner?
by Russell E Owen March 20, 2005

March 20, 2005

>Been lurking here for a while and quietly observing. > >I am looking for a programming language and preferably and IDE for a >young nephew wanting to dip his toes in the programming pool... >Is Python worth further investigating and how good are the IDEs? >Is there something along the lines of REALbasic VisualBasic >integrated interface/code style IDE available? >What are the specialities limits of the language? >Why learn Python rather than battle on and master C or more >particularly Objective C ? >Rather difficult to answer, but how different is the learning curve? > >Many thanks for any help. Hmmm...I suggest the following: Smalltalk: Squeak and VisualWorks NC are both free (the latter only for noncommercial use). Smalltalk is a lovely, simple really powerful language that includes: - powerful IDE and class browser with integrated debugger; smalltalk has the best development environment I've ever seen for a language because it includes live debugging, live changing of classes (want to fix a method? go ahead; the change propagates; fix it and continue on the fly) - really simple yet powerful language; one of the most elegant languges I've seen, though the syntax is a bit different than C and Python programmers are used to - very rich class library, including one of the nicest collection classes (lists, sets, etc.) available Between these two, squeak is smaller and more fun and includes a nifty GUI called Morphic; however it all runs in one big window (very non-Mac like). VisualWorks is more Mac-like (at least on a Mac) and more mature, but is much larger. Both are fully cross-platform (write once, run everywhere). One limitation to smalltalk is that it's not much good for simple scripting, hence simple text processing scripts and such. Python really shines there, so... Python. This is a really nice language and he'll be able to go far with it. However, based on what you said above, some of its limitations make me nervous: - there is no really well integrated GUI, unlike the suggestions above. You can do GUI programming, but you have to choose a 3rd party package and they are fully powerful, but the two main ones (Tkinter and wxPython) are somewhat clumsy and poorly documented. - hence there is no really first rate IDE (not to put down the IDEs that are there, but in comparison to smalltalk or RealBasic...) Note: python is built into MacOS X 10.2, but it's an outdated version missing some of the things that make the language sane (such as readlines support and a GUI package). Install the missing items or a better package (if you've been reading you've seen various options for that including at least one recent binary installer). I suggest learning those two (since their few weaknesses are complimentary), but you could also consider: Buy RealBasic. The knowledge is well worth the money! It's not a wonderful language, but not so bad either and if he already knows it, well...that's a huge leg up. Java. Not sure what the IDE situation is for MacOS X, but the language is reasonable (much saner than C++). The problem is that the need to declare the type of all objects makes it a clumsy and messy language compared to Python and Smalltalk. I suggest NOT using C++. The language is too arcane and messy. The object model is insanely complicated and the pitfalls fill volumes. Learn to program first, then learn C++ later if you really have to. -- Russell

3 3

ANN: PyObjC 1.3b1
by Bob Ippolito March 17, 2005

March 17, 2005

NOTE: This is an announcement for a BETA release of `PyObjC`_. Though we know it to be quite stable, and have been using it on a daily basis for quite some time, use it at your own risk. 1.3.0 will be out in a matter of days, but it is essential that we get some eyes on this! .. _`PyObjC`: http://pyobjc.sourceforge.net/ Installer package available from: http://pythonmac.org/packages/ (note that the installer also contains `py2app`_ 0.1.8) .. _`py2app`: http://undefined.org/python/#py2app Source: http://svn.red-bean.com/pyobjc/tags/pyobjc-1.3b1/ Version 1.3 (2005-03-??) ------------------------ - The bridge now maintains object identity across the bridge in both directions. Previous versions of the bridge only did this when bridging from Objective-C to Python. Exceptions: NSString and NSNumber do not have unique proxies. NSString never will have. Python numbers and strings are converted, not proxied and therefore also don't get unique proxies. And finally, any python object that is proxied using the ``__pyobjc_object__`` interface will only get a unique proxy if the ``__pyobjc_object__`` method implements that feature. - New ``objc.protocolsForClass`` function that returns a list of protocols that the class directly claims to conform to. - PyObjC classes can now declare that they implement formal protocols, for example:: class MyLockingClass(NSObject, objc.protocolNamed('NSLocking')): # implementation pass It is also possible to define new protocols:: MyProtocol = objc.formal_protocol("MyProtocol", None, [ selector(None, selector='mymethod', signature='v@:'), ]) All formal protocols are instances of ``objc.formal_protocol``. - PyObjCTools.KeyValueCoding has a new ``kvc`` class that allows Pythonic Key-Value Coding. - ``__getitem__`` is mapped to ``valueForKeyPath:`` - ``__setitem__`` is mapped to ``setValue:forKeyPath:`` - ``__getattr__`` is mapped to ``valueForKey:`` - ``__setattr__`` is mapped to ``setValue:forKey:`` The ``kvc`` class uses ``__pyobjc_object__``, so it may cross the bridge as the wrapped object. - ``NSNumber`` instances are bridged to a ``float``, ``long``, or ``int`` subclass that uses ``__pyobjc_object__``. ``NSDecimal`` is converted to ``NSDecimalNumber`` when used as an object, ``NSDecimalNumber`` is not bridged to ``NSDecimal`` because the latter is a mutable type. - The Python to Objective-C bridge now looks for a ``__pyobjc_object__`` attribute to get a PyObjC object from a Python object. - New IDNSnitch example in Inject that demonstrates how to write an monitor for the launch of another application, use ``objc.inject`` to load code into a target process, and override the implementation of an existing method but still call back into the original implementation (method swizzling). - ``objc.IMP`` should do the right thing now. This type is returned by ``+[NSObject methodForSelector:]`` and ``+[NSObject instanceMethodForSelector:]`` - New ToDos example in CocoaBindings that demonstrates how to use two array controllers for the same data, and how to use value transformers to alter the color of text. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New Bookmarks example in CocoaBindings that demonstrates how to subclass ``NSArrayController`` to implement the ``NSTableView`` delegate drag and drop protocol, including copying of objects between documents and accepting URL drops from other applications. Also demonstrates re-ordering of the content array. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New FilteringController example in CocoaBindings that demonstrates how to subclass ``NSArrayController`` to implement filtering of a ``NSTableView``. Also demonstrates the use of indexed accessors. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New ControlledPreferences example in CocoaBindings that demonstrates how to use Cocoa Bindings to simplify storing and retrieving user preferences. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New TemperatureTransformer example in CocoaBindings that demonstrates how to use NSValueTransfomers with PyObjC. Based on Apple's "Cocoa: Value Transformers" documentation, converted to PyObjC by u.fiedler. - New CurrencyConvBindings example in CocoaBindings that demonstrates a Cocoa Bindings enabled version of the CurrencyConverter example. Converted to PyObjC by u.fiedler from the example in Apple's "Introduction to Developing Cocoa Applications Using Bindings". - New ManualBindings example in CocoaBindings that demonstrates how to develop programmatic bindings from a PyObjC application. Converted to PyObjC by u.fiedler from the "Cocoa Bindings and Hints" example of the same name. - New HotKeyPython example in AppKit that demonstrates how to use Carbon global hot keys from a PyObjC application. Also demonstrates how to use a NSApplication subclass. - Key-Value Observing support is now automatic in Python classes that descend from ``NSObject``, unless they implement a custom ``willChangeValueForKey:``, ``didChangeValueForKey:``, or ``__useKVO__`` is not True. This allows ``self.foo = 1`` to automatically trigger notifications. This works in all cases, whether ``foo`` is a ``property``, ``ivar``, or just in the ``__dict__``. - New Inject folder in Examples, with an InjectInterpreter example that will inject a GUI Python interpreter into any process. - New ``objc.inject()`` function for Mac OS X 10.3 and later, allows an arbitrary bundle to be loaded into another process using mach_inject. - ``objc.classAddMethods`` now recognizes and supports classmethods. - GC is now correctly implemented for struct wrappers. - The ``NSNumber`` bridge has been removed, now you will get ``NSNumber`` instances across the bridge instead of a Python representation. - ``PyObjCTools.AppHelper.runEventLoop()`` will now bring your application to the front at startup when using pdb mode for convenience. - ``objc.loadBundle()`` no longer filters the class list. This solves a few potential issues and shaves off about 1/3rd of the overhead of ``python -c "import AppKit"``. - ``PyObjCTools.AppHelper.runEventLoop()`` no longer breaks on pure Objective-C exceptions. Most exceptions of this variety are more like warnings, and there is nothing that can be done them anyway. - ``PyObjCTools.AppHelper.runEventLoop()`` now installs the interrupt handler and verbose exception logging when using pdb, either explicitly or by the USE_PDB environment variable. - There is now a fast path for the ``NSString``/``unicode`` bridge when ``Py_UNICODE_SIZE`` is 2. This is the default setting for Python. - The default selector signature will have a void return value unless a "return" statement with an argument is used in the bytecode. In that case, it will default to an object return value. - ``__bundle_hack__`` is no longer necessary, py2app now sets a different environment variable to the current plugin during execution, and a hack is installed to ``NSBundle`` so that classes may respond to requests for their bundle with the ``+bundleForClass`` method. The class builder adds a default implementation of this to Python classes if this environment variable is set. - Added ``objc.currentBundle()``, which is equivalent to ``NSBundle.mainBundle()`` except after loading a plug-in. Makes it easier to load nib files. - ``PyObjCTools.NibClassBuilder.extractClasses()`` now uses ``objc.currentBundle()`` instead of ``NSBundle.mainBundle()``. This makes plugins less of a hassle to develop and allows identical code to be used for application or plugin development. - ``objc.registerPlugin()`` and ``objc.pluginBundle()`` are now deprecated as they are no longer useful. - It is now possible to subclass a class that implements ``copyWithZone:`` without setting ``__slots__`` to ``()``.

1 0

ANN: PyObjC 1.3b1
by Bob Ippolito March 17, 2005

March 17, 2005

NOTE: This is an announcement for a BETA release of `PyObjC`_. Though we know it to be quite stable, and have been using it on a daily basis for quite some time, use it at your own risk. 1.3.0 will be out in a matter of days, but it is essential that we get some eyes on this! .. _`PyObjC`: http://pyobjc.sourceforge.net/ Installer package available from: http://pythonmac.org/packages/ (note that the installer also contains `py2app`_ 0.1.8) .. _`py2app`: http://undefined.org/python/#py2app Source: http://svn.red-bean.com/pyobjc/tags/pyobjc-1.3b1/ Version 1.3 (2005-03-??) ------------------------ - The bridge now maintains object identity across the bridge in both directions. Previous versions of the bridge only did this when bridging from Objective-C to Python. Exceptions: NSString and NSNumber do not have unique proxies. NSString never will have. Python numbers and strings are converted, not proxied and therefore also don't get unique proxies. And finally, any python object that is proxied using the ``__pyobjc_object__`` interface will only get a unique proxy if the ``__pyobjc_object__`` method implements that feature. - New ``objc.protocolsForClass`` function that returns a list of protocols that the class directly claims to conform to. - PyObjC classes can now declare that they implement formal protocols, for example:: class MyLockingClass(NSObject, objc.protocolNamed('NSLocking')): # implementation pass It is also possible to define new protocols:: MyProtocol = objc.formal_protocol("MyProtocol", None, [ selector(None, selector='mymethod', signature='v@:'), ]) All formal protocols are instances of ``objc.formal_protocol``. - PyObjCTools.KeyValueCoding has a new ``kvc`` class that allows Pythonic Key-Value Coding. - ``__getitem__`` is mapped to ``valueForKeyPath:`` - ``__setitem__`` is mapped to ``setValue:forKeyPath:`` - ``__getattr__`` is mapped to ``valueForKey:`` - ``__setattr__`` is mapped to ``setValue:forKey:`` The ``kvc`` class uses ``__pyobjc_object__``, so it may cross the bridge as the wrapped object. - ``NSNumber`` instances are bridged to a ``float``, ``long``, or ``int`` subclass that uses ``__pyobjc_object__``. ``NSDecimal`` is converted to ``NSDecimalNumber`` when used as an object, ``NSDecimalNumber`` is not bridged to ``NSDecimal`` because the latter is a mutable type. - The Python to Objective-C bridge now looks for a ``__pyobjc_object__`` attribute to get a PyObjC object from a Python object. - New IDNSnitch example in Inject that demonstrates how to write an monitor for the launch of another application, use ``objc.inject`` to load code into a target process, and override the implementation of an existing method but still call back into the original implementation (method swizzling). - ``objc.IMP`` should do the right thing now. This type is returned by ``+[NSObject methodForSelector:]`` and ``+[NSObject instanceMethodForSelector:]`` - New ToDos example in CocoaBindings that demonstrates how to use two array controllers for the same data, and how to use value transformers to alter the color of text. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New Bookmarks example in CocoaBindings that demonstrates how to subclass ``NSArrayController`` to implement the ``NSTableView`` delegate drag and drop protocol, including copying of objects between documents and accepting URL drops from other applications. Also demonstrates re-ordering of the content array. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New FilteringController example in CocoaBindings that demonstrates how to subclass ``NSArrayController`` to implement filtering of a ``NSTableView``. Also demonstrates the use of indexed accessors. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New ControlledPreferences example in CocoaBindings that demonstrates how to use Cocoa Bindings to simplify storing and retrieving user preferences. Originally from "Cocoa Bindings Examples and Hints", converted to PyObjC by u.fiedler. - New TemperatureTransformer example in CocoaBindings that demonstrates how to use NSValueTransfomers with PyObjC. Based on Apple's "Cocoa: Value Transformers" documentation, converted to PyObjC by u.fiedler. - New CurrencyConvBindings example in CocoaBindings that demonstrates a Cocoa Bindings enabled version of the CurrencyConverter example. Converted to PyObjC by u.fiedler from the example in Apple's "Introduction to Developing Cocoa Applications Using Bindings". - New ManualBindings example in CocoaBindings that demonstrates how to develop programmatic bindings from a PyObjC application. Converted to PyObjC by u.fiedler from the "Cocoa Bindings and Hints" example of the same name. - New HotKeyPython example in AppKit that demonstrates how to use Carbon global hot keys from a PyObjC application. Also demonstrates how to use a NSApplication subclass. - Key-Value Observing support is now automatic in Python classes that descend from ``NSObject``, unless they implement a custom ``willChangeValueForKey:``, ``didChangeValueForKey:``, or ``__useKVO__`` is not True. This allows ``self.foo = 1`` to automatically trigger notifications. This works in all cases, whether ``foo`` is a ``property``, ``ivar``, or just in the ``__dict__``. - New Inject folder in Examples, with an InjectInterpreter example that will inject a GUI Python interpreter into any process. - New ``objc.inject()`` function for Mac OS X 10.3 and later, allows an arbitrary bundle to be loaded into another process using mach_inject. - ``objc.classAddMethods`` now recognizes and supports classmethods. - GC is now correctly implemented for struct wrappers. - The ``NSNumber`` bridge has been removed, now you will get ``NSNumber`` instances across the bridge instead of a Python representation. - ``PyObjCTools.AppHelper.runEventLoop()`` will now bring your application to the front at startup when using pdb mode for convenience. - ``objc.loadBundle()`` no longer filters the class list. This solves a few potential issues and shaves off about 1/3rd of the overhead of ``python -c "import AppKit"``. - ``PyObjCTools.AppHelper.runEventLoop()`` no longer breaks on pure Objective-C exceptions. Most exceptions of this variety are more like warnings, and there is nothing that can be done them anyway. - ``PyObjCTools.AppHelper.runEventLoop()`` now installs the interrupt handler and verbose exception logging when using pdb, either explicitly or by the USE_PDB environment variable. - There is now a fast path for the ``NSString``/``unicode`` bridge when ``Py_UNICODE_SIZE`` is 2. This is the default setting for Python. - The default selector signature will have a void return value unless a "return" statement with an argument is used in the bytecode. In that case, it will default to an object return value. - ``__bundle_hack__`` is no longer necessary, py2app now sets a different environment variable to the current plugin during execution, and a hack is installed to ``NSBundle`` so that classes may respond to requests for their bundle with the ``+bundleForClass`` method. The class builder adds a default implementation of this to Python classes if this environment variable is set. - Added ``objc.currentBundle()``, which is equivalent to ``NSBundle.mainBundle()`` except after loading a plug-in. Makes it easier to load nib files. - ``PyObjCTools.NibClassBuilder.extractClasses()`` now uses ``objc.currentBundle()`` instead of ``NSBundle.mainBundle()``. This makes plugins less of a hassle to develop and allows identical code to be used for application or plugin development. - ``objc.registerPlugin()`` and ``objc.pluginBundle()`` are now deprecated as they are no longer useful. - It is now possible to subclass a class that implements ``copyWithZone:`` without setting ``__slots__`` to ``()``.

1 0