On Jan 31, 6:40 pm, Thomas Schreiber <t...@insatsu.us> wrote: > I am extremely satisfied with Homebrew for OSX packet > management:http://github.com/mxcl/homebrew > > Much cleaner to customize and get right than macports, fink, or manual > building. New recipes get added all the time, and most everything I've > needed is already there. > > With home brew I never touch anything in System python, and I simply use it > to install 2.6.4 as my main python. > I run easy_install pip, pip install virtualenv and using virtualenvwrapper, > install any other packages into project relevant virtualenvs, always > creating with --no-site packages.
But did you ever try using mod_wsgi? >From problems some have had in using homebrew with mod_wsgi, it seems worse than MacPorts and fink when it comes playing nice with embedded systems. The default installation of Python in homebrew appears not to even supply a dynamic Python library or framework that can be linked in an embedded system. Graham > On Sat, Jan 30, 2010 at 22:55, Graham Dumpleton > <graham.dumple...@gmail.com>wrote: > > > > > > > On Jan 31, 4:11 pm, Dave Murphy <d...@schwuk.com> wrote: > > > On 30 January 2010 20:26, Sector7B <joe.greenaw...@gmail.com> wrote: > > > > > Hi, I thought I would share some insight into getting django up and > > > > running in Mac OS X after about a day or two of frustration. > > > > > Step 1: Abandon all Apple supplied tools, and switch to using macports > > > > for everything. I could be missing something and someone could say > > > > they had no problems and if so good for them. But once I moved all my > > > > development using macports everything just worked. > > > > Disagree almost completely. I'm happily developing Django using the > > > Apple supplied Python and tools, although I have complemented them > > > with virtualenv and pip. > > > > The only sore spot in my development stack is that I can't get > > > psycopg2 to work (due to issues with 32/64-bit in SL), but I simply > > > work around that by using SQLite in development and PostgreSQL in > > > staging/production. Don't use MySQL, so can't comment on that. > > > > Oh, and just because anecdotal experience is complete subjective, I've > > > had nothing but hassle from using the likes of Macports and Fink so I > > > wouldn't recommend them to anyone. > > > I'd agree, from the perspective of dealing with mod_wsgi questions all > > the time, both MacPorts and fink distributions are a PITA. > > > The Python distributions from MacPorts especially don't seem to be > > built properly and give lots of problems when being embedded in > > systems such as mod_wsgi due to runtime framework linkage not working > > properly. The MacPorts and fink distributions in the past, not sure > > about now, were never properly compiled as fat architecture binaries, > > which always gave problems with Apache supplied with MacOS X which > > will run in 64 bit mode by default. > > > So, OP may have not have problems, but that is because MacPorts may > > work with itself, but as soon as you try and use it with anything else > > or want to run stuff as 64 bit you more often than not get problems. > > > Graham > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@google > > groups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
