And you really don't want to use easy_install amymore, either. Try pip. I see the appeal of an Apple-supplied python, but Apple has never properly supported it ever since OS-X 10.1.....
-CHB On Fri, Apr 28, 2017 at 5:19 PM Glyph <gl...@twistedmatrix.com> wrote: > Relying on the system Python for this sort of stuff has always guaranteed > you'd have an out-of-date version of all of your dependencies. > > The availability of wheels (thanks again Ronald!!!) for pyobjc means that > you don't need the biggest impediment to users installing stuff, which is a > C compiler. If you're building stuff for distribution to non-technical > folks, build it with your own version of python (3) and ship it with > py2app, not by copying scripts around. > > If there are things that make this more painful than just copying > individual scripts, it's probably best to figure out how to get those > addressed with the PyPA community. > > -glyph > > > On Apr 28, 2017, at 4:20 AM, Ben Byram-Wigfield <ben...@me.com> wrote: > > > > I ran the installer package for the latest python 2.7, and then used > easy_install to install PyObjC. > > I get the same errors on two separate Macs. What should I do to fix the > installation? > > > > Does Apple not have plans to include (all of) the latest PyObjC? That’s > rather sad. The reason I was attracted to creating ObjC python scripts was > that they could run on any Mac. > > > > Thanks > > > > Ben > > > > > >> On 28 Apr 2017, at 08:07, Ronald Oussoren <ronaldousso...@mac.com> > wrote: > >> > >> > >>> On 27 Apr 2017, at 10:17, Ben Byram-Wigfield <ben...@me.com> wrote: > >>> > >>> I tried the repository browser there, and the version of > parse_page_contents.py still doesn’t work for me. I’m using the latest > downloaded versions of python 2.7 and PyObjC. I also tried using the > default OS X versions. > >>> The errors are in the attached file. > >>> > >> The PyObjC 3.2 error at the top of the file seems to indicate that your > Python installation is broken, PyObjC imports the stdlib io module and that > causes and error. > >> > >> The PyObjC 2.5 error is due to general brokeness of the system > installation of PyObjC. PyObjC 2.5 is ancient and not something I support > anymore, furthermore (IIRC) Apple doesn’t ship all of PyObjC. The error > you’re getting indicates that the framework wrappers are incomplete. > >> > >> BTW. If you are new to Python I’d look into using Python 3.6 instead, > both because that has less change to run into problems due to interference > between the system install of Python 2.7 and a manual installation, and > because the Python community is moving ever faster to Python 3. > >> > >> Ronald > >> > > > > _______________________________________________ > > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > > https://mail.python.org/mailman/listinfo/pythonmac-sig > > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG > -- Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG