On May 25, 5:24 pm, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Tue, May 25, 2010 at 2:41 PM, Graham Dumpleton > > > > > > <graham.dumple...@gmail.com> wrote: > > > On May 24, 7:37 pm, Russell Keith-Magee <freakboy3...@gmail.com> > > wrote: > >> Hi all, > > >> This is a reminder to everyone that DjangoCon.eu is on during this > >> week. Jacob, Jannis, myself, and several other prominent django-dev > >> contributors are in Berlin, and as a result, we may not be able to pay > >> as much attention to django-dev as would would normally. > > >> So - if you post a Grand Proposal for Django 1.3 Awesomeness, please > >> don't be offended if we don't respond as quickly as we would normally. > > >> We will be sprinting at the conference on Thursday and Friday. If you > >> have a detailed proposal that would benefit from some round-table > >> discussion while several core developers are in the same room, please > >> post your proposal and we'll try to discuss it. Alternatively, if you > >> wait until early next week, life should return to relative normality. > > >> Yours, > >> Russ Magee %-) > > > Be nice if you can work out direction on uniform Django entry point > > for hosting such that behaviour is always the same and not different > > between development server and other hosting mechanisms. For why this > > is a problem with WSGI hosting see my blog post at: > > > http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html > > > If don't see it as an issue, then if you are at Sydney PyCon I can > > find you there and we can argue about it. :-) > > Yes, I'll be at Pycon.AU, so we should certainly use the opportunity > to thrash out some details if we can. I'll try and get some of the > discussion started during the sprints so I'll be well armed by the > time PyCon comes around. > > > BTW, I have separate ideas about making WSGI hosting simpler, but been > > hard so far to get anyone interested. Part of the problem is that > > authors of each hosting mechanism are content with their own way of > > doing things and don't appear to really want to cooperate in coming up > > with one better standard interface. :-( > > Armin Ronacher has been singing a similar song this week. I agree that > Django hasn't been good at interacting with the broader community when > it comes to this sort of issue. I could come up with all sorts of > excuses for why this is the case, but excuses won't fix anything -- > ultimately we just need to do better.
>From what I understand of where Armin is coming from he wants to rewrite WSGI from scratch effectively based on everything we have learnt. I totally agree with that and have thought that for quite a while but saw it as a bit too hard to achieve. Momentum is changing though on this which is positive. What I am thinking of is not related to the WSGI interface itself but the mechanisms around creation and setup of the WSGI application for deployment. Not ready to explain it more at this point as don't really have the time and have preference for implementing a proof of concept as that would explain it better than any description. Graham -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
