[Pythonmac-SIG] Bundlebuilder--why remove it?

Charles Hartman charles.hartman at conncoll.edu
Thu Dec 10 01:26:09 CET 2009

I just want to add a vote (plea, whimper) from somebody who writes  
Python programs, doesn't feel particularly comfortable with Terminal  
or bash, and wants to be able to make distributable apps for Mac.  And  
keep making them as Python and associated libs get updated.  I may be  
wrong, but I think there are a whole lot of people like me, and in  
some sense we're an important part of the Python and Mac user base.   
 From this point of view, hardly anything in the P. & M. development  
world is more important than a reliable and easy-to-use version of  
py2app.  By the same token, interested as we are in all senses, we're  
pretty thoroughly unqualified to help with the development or even  
maintenance of the bundling code.

Charles Hartman

On Dec 9, 2009, at 4:17 PM, Ronald Oussoren wrote:

> On 9 Dec, 2009, at 14:08, Kevin Walzer wrote:
>> After spending some time getting bundlebuilder to work with my 64- 
>> bit programs, I have begun to wonder: what's the rationale for  
>> removing it from Python 3.X?
>> Its Carbon dependencies can be eliminated by simply removing the  
>> "import argvemulator" statement, so (as far as I can see) there is  
>> no serious technical impediment to leaving it in the Python  
>> library. Bundlbuilder doesn't really argvemulation anyway, since  
>> hooks for this exist in all the major GUI libraries (Tk, wxPython,  
>> and certainly PyObjC).
>> And while bundlebuilder is a less robust tool than py2app, it is  
>> nonetheless capable enough: I'm shipping two commercial  
>> applications that make use of it. In fact, its simplicity (a single  
>> module) make it easier to dig into and patch, something I can't do  
>> with py2app. I wouldn't have been able to release my applications  
>> without it.
> Py2app's code isn't that bad, although it does seem to be more  
> complex than needed. Refactoring is hard though due to a complete  
> lack of automated tests.
>> What's the best way to keep bundlebuilder available for Python 3.x?  
>> Submit a feature request at the bug tracker? Or separate it out,  
>> and submit a PyPi project?
> Separating it out would be better. I'm not interested in re-adding  
> bundlebuilder.
> What really should be done is restart py2app development, starting  
> with automated tests and improved egg support. I'd love to work on  
> that but basicly don't have time for that at the moment.
> Ronald_______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig

More information about the Pythonmac-SIG mailing list