Re: [Pyobjc-dev] Bundling trunk version of PyObjC

[Ronald O. <ron...@ma...>]

On 24 Nov, 2009, at 15:24, Orestis Markou wrote:

> 
> On 24 Nov 2009, at 16:20, Ronald Oussoren wrote:
> 
>> 
>> On 24 Nov, 2009, at 15:16, Orestis Markou wrote:
>> 
>>> On 24 Nov 2009, at 14:56, Ronald Oussoren wrote:
>>> 
>>>> 
>>>> On 24 Nov, 2009, at 8:19, Orestis Markou wrote:
>>>> 
>>>>> Hello,
>>>>> 
>>>>> I would like to use the latest version (SVN) of PyObjC in my applications, both on 10.5 and on 10.6 (10.6 ships with a version of PyObjC that doesn't work with my apps).
>>>>> 
>>>>> I'm having trouble building everything and getting it to work. I tried to modify the 02-develop-all.sh script to install instead of develop, but it seems not to be working. I will have to try again to give more information there.
>>>>> 
>>>>> Is there an easy way to produce a build of PyObjC + Frameworks that can be easily dropped into an app bundle and used?
>>>>> 
>>>>> The app should run on stock Python 2.5 on 10.5 and 10.6.
>>>> 
>>>> I'll  upload a new release to pypi later today. When that's done 'easy_install pyobjc==2.2' should work. 
>>>> 
>>>> PyObjC 2.2 will be the version that's currently in the repository, with updated version numbers.
>>> 
>>> Thanks for that - I'm still wondering how to do a full build from source though (in case I want to fix a bug or try out something new). Right now with easy_install I can't find any option that will allow me to point to a directory and say 'install from here'.
>> 
>> "python setup.py install" in the right order should work (that's what the develop.sh script does).  
>> 
>> I just noticed that you try to install an updated version of pyobjc in the system install of Python. I wouldn't do that, I know Apple used pyobjc in the past, and AFAIK still does so on the server. Upgrading PyObjC might break that code
> 
> Accidentally de-cced the list. Re-adding now.
> 
> I'm installing this into a clean virtualenv, and then copy all packages out. I may have to fiddle with .pth files a bit though to get everything working.
> 
> OK, so I do have to install every framework wrapper separately. I was hoping that since the dependencies are all listed in the 'empty' pyobjc project I could reuse that somehow. I will tweak develop.sh to do what I want and report back.

It's probably possible to tell easy_install to use files in a directory, something like the (untested):


   easy_install -f dir-containing-pyobjc-sources pyobjc=2.2

This probably requires sdist archives of all subprojects.  I'll see if I can come up with a better solution in pyobjc 2.3, possibly using a custom distutils command in the pyobjc package.

BTW. easy_install has a -l option that might help as well:

  --local-snapshots-ok (-l)      allow building eggs from local checkouts

While easy_install is pretty useful it is still far removed from being a truly usefull packaging tool. I'd love to see a real python package tool (and pip isn't it, that's in the end just a slightly different version of easy_install)

Ronald