Hello again, The features implemented in the patches are very important for us, so I'd be more than happy to help with the development of v1.2 so you can have more time to review these three patches.
We don't want to affect the development of Django 1.2, but at the same time we'd really prefer to have this included in Django officially, instead of having our patched version of Django. If any of you is interested in trading tickets, please let me know. ;-) Hoping-it-can-be-feasible'ly, - Gustavo. On Wed, 2009-10-28 at 09:58 +0000, Gustavo Narea wrote: > Hello, Russell. > > OK, I see what you mean, it sounds sensible. > > Then I'd really appreciate if a core developer could take a look into > this. I think the advantages are very important, we're talking about > making Django more interoperable with other applications, and it'd > require little effort on your side: > - The patch for ticket 12075 is totally trivial. There can't be any > backwards incompatibilities. > - The patch for ticket 8927 is not trivial, but it's not complex > either. It's basically all about making the WSGI environment dictionary > available in mod_python, so the HttpRequest object can have a common API > across handlers. > - The patch for ticket 12091 is a bit complex, but it's a whole new > feature, we're not modifying an existing behavior (i.e., there can't be > backwards incompatibilities)... And, it has a unit test suite which > covers 100% of the new module. > > I'd agree ticket 8927 is not that relevant to be included at this point > in the 1.2 branch, but for both #12075 and #12091, the WSGI environment > must be available. > > If it helps, I could also write documentation for the above and send you > another patch. > > Please let me know what you think, > > - Gustavo. > > > On Wed, 2009-10-28 at 08:24 +0800, Russell Keith-Magee wrote: > > On Tue, Oct 27, 2009 at 10:49 PM, Gustavo Narea > > <gustavona...@2degreesnetwork.com> wrote: > > > > > > Hi there. > > > > > > Over the last week I've been working to improve WSGI support in Django > > > and I have sent a few patches which have not received the feedback I > > > expected to have, so I wanted to ping you. ;-) > > > > In the interests of good community relations, I want to clarify the > > feedback you should be expecting. > > > > Just because you've uploaded a patch doesn't mean you're going to get > > immediate feedback. We're all volunteers, so our time is limited - > > sometimes, this means that patches don't get triaged for a while. > > Patience is required. > > > > On top of that, we've just finished our feature discussion phase, and > > we have nominated the features that are a high priority for the > > project [1]. These are the features that will be receiving development > > priority over the next few months. Features that aren't on this list > > aren't going to get the immediate attention of the core team. > > > > The feature list isn't completely locked off, though. Any feature with > > a complete patch is potentially on the list for inclusion. However, > > any feature that isn't on the list will require: > > > > 1) A champion in the core team to commit the code > > 2) A design and implementation that has been approved by the community > > (as evidenced by discussion on django-dev) > > > > That means you're going to need a member of the core team who is > > excited about this possible feature. I can't speak for the other > > members of the core team, but personally, this isn't a big itch. I can > > certainly see how it could be useful, but I've already committed to > > some big-ticket items that are much higher priorities for me > > personally. > > > > So - you need to have some patience. If you can't get a core developer > > engaged as a result of this thread, you may need to wait until the > > v1.3 feature discussion phase, which will open as soon as v1.2 is > > finalized. Alternatively, you could help out with the features that we > > have already agreed upon for v1.2, and maybe try to leverage the karma > > you gain from doing that work into support for your WSGI patch. > > > > [1] http://code.djangoproject.com/wiki/Version1.2Features -- Gustavo Narea. Software Developer. 2degrees, Ltd. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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 -~----------~----~----~----~------~----~------~--~---
