[Pythonmac-SIG] Why Do I Explicitly Need MacPython

Ronald Oussoren ronaldoussoren at mac.com
Tue Sep 26 10:45:44 CEST 2006

On Sep 26, 2006, at 10:23 AM, konrad.hinsen at laposte.net wrote:

> On 22.09.2006, at 18:51, Bob Ippolito wrote:
>>> Get Py2app, then use:
>>> bdist_mpkg
>> bdist_mpkg -z will produce a zipped .pkg and save you a step...
> bdist_mpkg works fine for me, but I would like to distribute my
> packages with added documentation. Is there any way to add a
> documentation package to the mpkg created by bdist_mpkg? Or are there
> convenient (i.e. scriptable) tools for adding it in the end?
> Another limitation I ran into is dependencies. I don't mind writing
> test scripts by hand, but it would be nice if I could integrate them
> into the mpkg as part of an automated build procedure. At the moment
> I hardly ever update my Mac packages because it's too much manual  
> work.

You can use bdist_mpkg from the setup script and add additional  
subpackages that way. PyObjC uses this to ship the examples and Xcode  
templates, this is implemented setup-lib/pyobjc_mpkg.py in the PyObjC  

PyObjC's installer also used to include dependencies, but that  
functionality got dropped with the move to setuptools. I want to  
restore this functionality because as you said it is very convenient  
to have a single installer that installs a  package and all of its  
dependencies, even in a world where setuptools exists.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3562 bytes
Desc: not available
Url : http://mail.python.org/pipermail/pythonmac-sig/attachments/20060926/31ae39d4/attachment.bin 

More information about the Pythonmac-SIG mailing list