Re: [Pyobjc-dev] Getting started confusion

[Scott H. <sco...@gm...>]

Thanks for the info. I installed the XCode templates and got a demo program up and running last night using the stock PyObjC. Trying out mixing ObjC and Python and calling each language from the other. It's falling into place.

-Scott
On May 14, 2010, at 2:35 AM, James R Eagan wrote:

> Hi Scott,
> 
> You should be able to stick with the system-supplied PyObjC for most cases.  There have been some bugs fixed since that version, but for the most part, they are minor (although the definition of "minor" will depend on which libraries you need to use).
> 
> For what it's worth, I'm still using a (mostly) stock 10.6.3 Python/PyObjC setup for all of my development.  The only changes I've made are to fix a couple of bugs in py2app relating to 1) alias builds and 2) plugin builds (see below).  (I believe that Ronald has already incorporated these fixes in SVN.)
> 
> Cheers!
> James
> 
> 
> [1]:
> Jagaroth:/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/pyt
> hon/py2app $ diff -u build_app.py.orig build_app.py
> --- build_app.py.orig	2009-07-01 08:26:30.000000000 +0200
> +++ build_app.py	2009-11-02 11:49:57.000000000 +0100
> @@ -1090,7 +1090,12 @@
>  
>          # symlink python executable
>          execdst = os.path.join(appdir, 'Contents', 'MacOS', 'python')
> -        self.symlink(sys.executable, execdst)
> +        prefixPathExecutable = os.path.join(sys.prefix, 'bin', 'python')
> +        if os.path.exists(prefixPathExecutable):
> +            pyExecutable = prefixPathExecutable
> +        else:
> +            pyExecutable = sys.executable
> +        self.symlink(pyExecutable, execdst)
>  
>          # make PYTHONHOME
>          pyhome = os.path.join(resdir, 'lib', 'python' + sys.version[:3])
> 
> 
> [2]:
> Jagaroth:/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/pyt
> hon/py2app/bootstrap $ diff -u boot_plugin.py.orig boot_plugin.py
> --- boot_plugin.py.orig	2006-07-11 22:31:34.000000000 +0200
> +++ boot_plugin.py	2009-11-16 13:35:27.000000000 +0100
> @@ -5,6 +5,7 @@
>      base = os.environ['RESOURCEPATH']
>      site.addsitedir(base)
>      site.addsitedir(os.path.join(base, 'Python', 'site-packages'))
> +    site.addsitedir(os.path.join(sys.prefix, 'Extras', 'lib', 'python'))
>      for script in scripts:
>          path = os.path.join(base, script)
>          __file__ = path
> 
> 
> 
> 
> Le 13 mai 2010 à 21:35, Scott Harris a écrit :
> 
>> I'm running on 10.6.2 with no other Python than the Apple supplied version.
>> 
>> After looking a the docs and mailing list I'm still a bit confused.
>> 
>> If I do this: "easy_install pyobjc==2.2"
>> I'll end up installing 2.2 over the 2.2b3 that comes with my system and that's bad, right?
>> 
>> So should I install another version of Python and make sure that that python is in front of the system Python in my path so that I install PyObjC against that?
>> 
>> Can I just stick with the supplied version of PyObjC and python? What's the downside there?
>> 
>> What's the recommended setup for PyObjC development? 
>> 
>> Thanks,
>> -Scott
>> 
>>  
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 
> --
> James R. Eagan
> LRI — Bâtiment 490
> Université de Paris-Sud XI          email: Jam...@lr...
> 91405 Orsay Cedex — France          web: http://www.lri.fr/~eaganj
>