|
Ben Davies
omarshariffdontlikeit at gmail.com
Sat Mar 8 20:04:03 EST 2008
"Removing the OS supplied Python is a really bad idea and you may now have potentially broken parts of your operating system that depend on it." Wah-hay! And here me thinking I knew what I was doing! Been a while since I've hosed a system. At least this time I didn't get that awful sinking feeling after pressing delete. Actually, thats more of a worry... :) "I always recommend not installing a newer version of Python on MacOS X Tiger unless you know what you are doing. :-)" I don't think there is a better description of my recent actions! "After you have fixed your OS, personally I would suggest that since you are new to Python not to bother with mod_python initially." Although my description of my actions might suggest this, I feel pretty comfortable (maybe inaccurately so, given the consequences of my actions over the last 48 hours!) that I might be alright with mod_python: the different phases of processing in Apache, OOP and the concept of frameworks etc; I am quite comfortable with: in fact the technical features of mod_python are what drew me to python in the first place. PHP5 has some glaring deficiencies in its OOP features that have driven me here (difficulty in accessing the low-level HTTP sub-system, lack of late-static binding and non-existent namespacing for 3), and I've found myself seeking lower/tighter integration with apache over the past 6 months or so. I figure that a lot of pythons features I understand, and that it should be merely new syntax that I need to learn (ha! get ready for a deluge of help requests!) "learn one of higher level frameworks such as Django or Pylons. These can be run with their own internal Python web servers." Like I say, concepts like MVC, ORM etc; I understand, having written my own PHP5 frameworks before. I'm really interested in REST and I feel that PHP's reluctance to provide closer integration with apache really puts it in a bind. I don't want compare features here, as I think I may already be preaching to the choir, but clean access to, for example, apache's filtering mechanism is really the direction I want to be heading in. It's taken me a long time to really get comfortable with Apache, and now I feel that it is seriously one of the greatest pieces of software ever written (2nd only to Portal :) ). I want to dive in, get my feet wet and give mod_python a whirl! If I have buggered my OSX install, then I think that the features of mod_python are enough to warrant a re-install, but I appreciate the reality check: the reality is though I need to move to mod_python ASAP. PHP just doesn't cut it anymore. Right, time to sign off. Apologies in advance, Budvar and portal make Ben a sleepy boy. Cheers, Ben On Sat, Mar 8, 2008 at 11:22 PM, Graham Dumpleton < graham.dumpleton at gmail.com> wrote: > On 09/03/2008, Ben Davies <omarshariffdontlikeit at gmail.com> wrote: > > Can anyone help me? I've been fiddling about with this mess for about 48 > > hours now and I'm so close to getting this working I can taste it! Heres > a > > quick summary: > > > > - I may have installed python 2.3 in the past > > No you didn't, it came with the operating system. > > > - I installed python 2.5, but it appears that it did not replace all > the > > references to 2.3, because > > I always recommend not installing a newer version of Python on MacOS X > Tiger unless you know what you are doing. :-) > > > - apache/mod_python complains about a missing 2.3 framework, which > > - I, in a spate of backspace frenzies, deleted, thinking I wouldn't need > it, > > cos I have 2.5 installed, which has its own framework files located > > elsewhere > > Removing the OS supplied Python is a really bad idea and you may now > have potentially broken parts of your operating system that depend on > it. Unless you can copy back the bits you deleted from another copy of > same OS, you may have to reinstall the OS. > > In short, on MacOS X, you should never delete anything under > /System/Library as this is the operating system area. Any user code > packages should get installed under /Library if it did so and only > really safe to remove stuff out of there, but only if again you have > also removed any dependencies. > > After you have fixed your OS, personally I would suggest that since > you are new to Python not to bother with mod_python initially. > Instead, learn one of higher level frameworks such as Django or > Pylons. These can be run with their own internal Python web servers. > At lowest level they use WSGI which allows them to be deployed to > various web hosting solutions if you ever get as far as a production > system. > > So, first step is to get Python 2.3 working again. After that I'd even > suggest you get rid of Python 2.5 and just use Python 2.3 for the time > being. If learning Python you aren't going to miss much by doing this. > > Graham > > > Other than that, I'm impressed at how easy this has been so far :) > Python > > looks great, and mod_python has some features that PHP just cant compete > on > > (creating custom apache filters in python? sweet!) > > > > Oh, and on top of all this, I suppose I should learn python itself :) > Anyone > > recommend any good books? I hear that the O'Rielly Programming Python > book > > is great. > > > > Thanks for your help, in advance! > > > > Cheers, > > > > Ben > > > > > > > > _______________________________________________ > > Mod_python mailing list > > Mod_python at modpython.org > > http://mailman.modpython.org/mailman/listinfo/mod_python > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20080309/42a055ac/attachment-0001.html
|