[Pythonmac-SIG] Fink vs MacPorts vs Framework
I currently use a Framework of 2.6.2 for my Python work but I always see a lot of posts about using Fink or MacPorts builds. Could anyone shed some light on why they use these rather than a Framework? Advantages/disadvantages? Thanks, Dan ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
Hi ! Seems to me there are a lot of python packages that are available through the MacPorts. In the built-in framework, there are only a few basic packages. Fink gives the same benefits than MacPorts, but there might be fewer packages available though it than through MacPorts. That's why I use MacPorts. Is this right ? a 2009/6/30 Dan Ross d...@rosspixelworks.com: I currently use a Framework of 2.6.2 for my Python work but I always see a lot of posts about using Fink or MacPorts builds. Could anyone shed some light on why they use these rather than a Framework? Advantages/disadvantages? Thanks, Dan ___ Pythonmac-SIG maillist - pythonmac-...@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig -- Alexandre Quessy http://alexandre.quessy.net/ ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
I'm not sure I understand what you mean. I can certainly add any packages I like to my Framework build so I don't think availability of packages is a concern. Unless I'm misinterpreting the term packages? On Tue, June 30, 2009 8:11 am, Alexandre Quessy wrote: Hi ! Seems to me there are a lot of python packages that are available through the MacPorts. In the built-in framework, there are only a few basic packages. Fink gives the same benefits than MacPorts, but there might be fewer packages available though it than through MacPorts. That's why I use MacPorts. Is this right ? a 2009/6/30 Dan Ross d...@rosspixelworks.com: I currently use a Framework of 2.6.2 for my Python work but I always see a lot of posts about using Fink or MacPorts builds. Could anyone shed some light on why they use these rather than a Framework? Advantages/disadvantages? Thanks, Dan ___ Pythonmac-SIG maillist - pythonmac-...@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig -- Alexandre Quessy http://alexandre.quessy.net/ ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
On Jun 30, 2009, at 12:11 PM, Dan Ross wrote: I'm not sure I understand what you mean. I can certainly add any packages I like to my Framework build so I don't think availability of packages is a concern. Unless I'm misinterpreting the term packages? Pygame for example, that is a pain to build right, is avaliable in macports, the same with subversion bindings and so on. The macport version of python 2.5 and 2.6 is a framework build so it is almost the same as the default leopard python sans dtrace support and probably the same as python.org ones. So it is just advantages in using the macports one I think :) -- Leonardo Santagada santagada at gmail.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
Leonardo Santagada wrote: On Jun 30, 2009, at 12:11 PM, Dan Ross wrote: I'm not sure I understand what you mean. I can certainly add any packages I like to my Framework build so I don't think availability of packages is a concern. Unless I'm misinterpreting the term packages? Pygame for example, that is a pain to build right, is avaliable in macports, the same with subversion bindings and so on. The macport version of python 2.5 and 2.6 is a framework build so it is almost the same as the default leopard python sans dtrace support and probably the same as python.org ones. So it is just advantages in using the macports one I think :) This is the main reason to use a packaging system like MacPorts or Fink--if you have a complicated set of libraries to build, they can streamline things. Otherwise there is no particular advantage to using them. -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
That makes a great deal of sense. I tried to mess with pygame at one time, but as you stated, it was such a pain to build I gave up. Leonardo Santagada wrote: On Jun 30, 2009, at 12:11 PM, Dan Ross wrote: I'm not sure I understand what you mean. I can certainly add any packages I like to my Framework build so I don't think availability of packages is a concern. Unless I'm misinterpreting the term packages? Pygame for example, that is a pain to build right, is avaliable in macports, the same with subversion bindings and so on. The macport version of python 2.5 and 2.6 is a framework build so it is almost the same as the default leopard python sans dtrace support and probably the same as python.org ones. So it is just advantages in using the macports one I think :) -- Leonardo Santagada santagada at gmail.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
My experience shows me that using fink or macports with python framework create problems with version mismatches and library duplication. So now, I only use the framework because i want to learn. With a little patience and trying a lot (with the help of google), I gradually install what I want, even pygame pygame but I must admit it was a bit complicated -- View this message in context: http://www.nabble.com/Fink-vs-MacPorts-vs-Framework-tp24271594p24276543.html Sent from the Python - pythonmac-sig mailing list archive at Nabble.com. ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Trying to use appscript need some help
Jan Erik Moström wrote: I'm trying to learn how to use appscript but I don't understand what I'm missing. I want to read photo info from iPhoto and have things working ... partly [...] # set ptitle to date of item 1 of the selection # app(u'iPhoto').selection.items[1].date.get() print 'Date : ', item.date.get() # AttributeError: Unknown property, element or command: 'date' The problem is the line where I try to get the date info, the first commented line is the applescript line I'm trying to translate, the second is what ASTranslate tells me, and the third is the error message I get. ASTranslate is wrong here; it should be 'date_' with a trailing underscore, not 'date'. In situations where application-defined terms conflict with built-in terms (i.e. use the same keyword but a different four-char code), appscript appends an underscore to the application-defined term to prevent any problems. There was a known inconsistency in how older versions of appscript applied these escapes; that has been fixed in the latest appscript and ASDictionary releases, but I've not had time to update ASTranslate yet. Meantime, if in doubt, go by the appscript-style dictionary, which you can export as HTML from ASDictionary or browse via appscript's built- in help() method (see the appscript manual for details). HTH has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Fink vs MacPorts vs Framework
Thanks but I do not want MacPorts or fink, I want to do it myself with only the tools of mac os x -- View this message in context: http://www.nabble.com/Fink-vs-MacPorts-vs-Framework-tp24271594p24278207.html Sent from the Python - pythonmac-sig mailing list archive at Nabble.com. ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] MacPython v2.5 on OS 10.5 yet?
On http://www.python.org/download/mac/ we read Python comes pre-installed on Mac OS X, but due to Apple's release cycle, it's often one or even two years old. The overwhelming recommendation of the MacPython community is to upgrade your Python by downloading and installing a newer version from the Python standard release page. If you are using Mac OS X 10.5, see the Leopard wiki page for detailed information. The Leopard wiki page (http://wiki.python.org/moin/MacPython/Leopard) says Python releases have progressed far enough that it may be worth installing the current MacPythondistribution, however there may be conflicts between MacPython installations and Mac OS X development tools, such as problems building PyObjC applications in Xcode. Mac OS X 10.5.x (Leopard) comes with the 2.5.1 Python distribution pre- installed, with an integrated Python Launcher.app. At the time of Leopard's launch, the official release version of Python was also 2.5.1. So some users may wish to avoid installing the pythonmac.org distribution and use the built-in python. (EditText (last edited 2009-04-28) Is this still current? Have the issues been resolved to the point of being able to unconditionally recommend say v2.5 or 2.5 on OX10.5? David Worrall. - Experimental Polymedia: worrall.avatar.com.au - Sonification: www.sonifiction.com.au - Education for Financial Independence: www.mindthemarkets.com.au ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] MacPython v2.5 on OS 10.5 yet?
On 30-Jun-09, at 9:16 PM, Leonardo Santagada wrote: I remember that Google App Engine had troubles with default python on osx. Also there was probably a reason for python versions 2.5.2, 2.5.3 and 2.5.4 be released (and you could look on the changelog). I would say that if none of the bugs that were fixed on python 2.5.1 onward affect you, you have no need to upgrade. Google App Engine, do you mean the dev environment? You're probably better off using Python.org Python for that, yes, since the 10.5 System Python predates GAE by a fair while. .. What I don't understand is why apple doesn't update the python package on new minor releases... they do ship some new libraries why not python? In short, not many system-critical apps depend on Python (if any) and Apple just doesn't see it a big enough deal to commit resources to updates. I don't think they update Ruby or Perl either (irb --version tells me I'm running a release from 2005). If you disagree, you should voice your concern to Apple. Also, Python.org provides binaries for the most up-to-date releases, and users of course are free to build it from source themselves. AFAIK PyObjC now easy_install's fine with these builds, so the only thing missing will be the closed-source stuff that Apple doesn't make public (i.e. the CoreGraphics SWIG wrappers which seem to be leaky anyway). David ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
