On Jan 26, 1:19 am, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Sun, Jan 25, 2009 at 10:45 PM,Almad<b...@almad.net> wrote: > > I still feel kinda weird that I must hack around Django so much to > > make basic testing things working :-]]] > > Let's be clear here - the "basic testing" thing that is failing here > is a very specific, and somewhat esoteric edge case - the case of a > view that invokes, via HTTP, another view on the same server.
No, case we're talking about is a test that calls one view multiple times in a row - and that is enough to have a problem with dev server. Which I insist on calling basic testing when we're talking about web application. > The Django core team has (repeatedly) made a very deliberate decision > to keep the development server single threaded. There are many very > good web servers out there - Django isn't trying to get into the game > of competing with any of them. We view Django's job as providing a > good web stack for a real web server to use; the development server is > provided as a convenience, nothing more. Yes, through it's very useful for testing. > Having a singlethreaded server makes the implementation much simpler, > so we can concentrate our efforts on making a great web stack, rather > than wasting effort on writing, debugging, and maintaining a web > server that we don't really want people to use for serious work. OK, if it's not meant for serious development and testing work, I guess it's OK then. (I'd just say that opitional multithreading contained in 10-line long patch is not so complicated) > A multithreaded server would also act as a tacit encouragement to use > Django's development server for real deployments, which we _really_ > don't want to encourage. If people start using Django's development > server in production, we would have to start treating it as a > production-ready server - doing security and performance audits and > the like - and again, this distracts us from what we consider to be > the "main game". OK, if community is expected to ignore 'do not use this option for production or you'll be banned from all our communication channels on first complaint', I guess nothing can be done. i guess PHP users are our target group. > The _only_ type of view that is affected by this decision is the view > that uses urllib (or equivalent) to invoke another view on the same > server. Yes, that's the only type of view affected. And some tests... > We (the Django core team) have decided that this is a > compromise we can live with. The set of cases where this behavior is > required is very small, doesn't form a part of the requirements for > most (almost all) web development projects. For that small subset of > users that _do_ have a legitimate use for this, there are some > lightweight multithreaded options (like CherryPy) out there, and to > the best of my knowledge, none of these options _require_ the patching > of core in order to use them. Well, after I fall into small group of users that do some automatized acceptance testing (and thus require, like, Selenium) and discovered that things looks like working after I lobotomized Django and replaced it with CherryPy, I'm now satisfied. > Yours, > Russ Magee %-) Almad P.S.: Sorry for the sarcastic tone of my e-mail. I appreciate Your work as well as Django framework (or at least some parts of it), but I just don't get it: for each and every project I've written in Django, I banged my head against the wall because of some issues that prevented me from normal testing - and were rejected by devs because of 'esoteric edge case'...and then reading 'Testing Django apps' on first presentation slide, 'because it's most important'. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
