Not hurt Malcolm. In fact I really try to avoid asking at the list, trying to google first, and I really appreciate the work of guys like you and Graham. I confess I don't have the patience enough to run a mailing list. And you guys here are pretty much helpful, like Karen for example, besides you two. But sometimes I got frustrated too... I am suposed to be a scientist, doing research, writing papers than code, but I really really like coding. And Django has been quite a pleasure.
However, straight deadlines, lots of hurdles (related to our server and applications), having to learn something new in a fortnight and when you think you're done, here comes another task, learn apache. But that's ok, I am starting to get the stuff. Anyway, although about "...Django will provide recipes for doing stuff that is out of scope and should remain so", don't get it wrong but setting up an apache is not out of scope of Django IMHO. Great if Django site has this stuff there, but a link sometimes is pretty much all that we need. For example, I only realise here in the list that is Graham who developed mod_wsgi and not from Django site (OK, if I had read more there I would find it too, but, gosh, the day has only 24 h and I have no clones). All the best. Cheers, Alan PS: to not mention that we have "life" as well, in my case a baby daughter and a wife who ordered me to clean the house now (apache and wsgi later). On Sat, Jan 10, 2009 at 10:58, Malcolm Tredinnick <malc...@pointy-stick.com>wrote: > > On Sat, 2009-01-10 at 10:37 +0000, Alan wrote: > > Thanks Graham, indeed I was being stupid, I didn't realise that mac > > leopard holds apache 2.2 now... > > > > > > About docs, where can I find something about apache2 + mac osx + > > mod_wsgi in http://docs.djangoproject.com or google? All I get is > > puzzles with missing pieces... > > So, here's the thing: one day we'll include a short piece on the really > basic setups for mod_wsgi in the Django docs, similar to what we do for > mod_python. We'll do that because somebody will write it (or one of the > rest of use will eventually find the time). However, it will never > replace the mod_wsgi documentation. Deliberately. > > The Django project shouldn't have to provide that kind of one-stop > replacement. The Django documentation is about using Django. For > documentaiton on using Apache, there is wonderful documentation provided > by the Apache project. For documentation on using Python, python.org is > the source. For documentation on using mod_wsgi, there is the mod_wsgi > project at Google. You can see the pattern here. Particularly when > external resources provide good documentation (python, Apache, mod_wsgi, > mod_python, etc, etc), we absolutely should dispatch to them (and Google > and Yahoo are our friends in this respect). I think it's absolutely > fantastic that somebody like Graham Dumpleton spends so much time on a > list like django-users when he doesn't have to. It provides a lot of > people with a lot of help. I also find it to be a form of highly > wasteful time usage, since most of the questions have more appropriate > forums and there's not always the "teach a man to fish" result falling > out at the end. Glad Graham does not, not about to pick up the slack if > he ever decides to ask people to come to the appropriate lists to ask > questions. > > We document how to use Django. We also go the extra mile and include a > bunch of other documentation to help out people just starting out (for > example, a lot of examples and explanations are somewhat verbose because > we're helping out Python beginners, which aren't our primary audience), > but it always has the slight side-effect of actually making the Django > documentation harder to use. The extra explanations of stuff that isn't > Django related often tends to obscure the actual useful Django > documentation. > > I'm not intending to be harsh here, but that is the reality. If somebody > is going to develop using Apache, then the same as if they're going to > use HTML or Javascript or Python or CSS or Eclipse or vim or whataver, > they have to be spend some time reading and learning about that tool. > Yes, it's a huge learning curve to develop web applications. It's > actually hard stuff. > > This isn't targeted (only) at you. It's a general complaint against > people hoping Django will provide recipes for doing stuff that is out of > scope and should remain so. > > Regards, > Malcolm > > > > > > -- Alan Wilter S. da Silva, D.Sc. - CCPN Research Associate Department of Biochemistry, University of Cambridge. 80 Tennis Court Road, Cambridge CB2 1GA, UK. >>http://www.bio.cam.ac.uk/~awd28<< --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
