I was a little skeptical at first to "pollute" the Mac environment with external python packages (i.e. I use pygments for my qa-stack.com application) this is the reason why I was relying in my (Linux) VM image for all the dirty work, in my reality, in Linux it is easier to manage different packages for different python versions, for example, the mercurial version for OS X is tied up to python 2.6, now with OS X Lion coming up soon, it will surely break hg, so this is an extra thing to consider.
On the other hand, python is fully supported in OS X - all it took me to install pygments in my Mac was an "easy_install pygments" (setuptools is already part of the package!), they (apple) made it extremely easy to install any python module or program (including web2py) that it became ridiculously simple, albeit you need to use iTerm or other console app and somewhat "know" what you're doing. Julio On Apr 21, 1:55 pm, pbreit <pbreitenb...@gmail.com> wrote: > Yeah, probably wouldn't hurt to steer more Mac users to source. From the > Download page, it seems Mac users should download the Mac package. > > If you use version control (if you don't, you should!) it's even better to > clone it from Google code. Then you can easily control your web2py version.
