http://sjservices.com/find11.html
--
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
Hi,
this week was the first week with official coding for my GSoC project. I
merged Bruno Renié's template based widget rendering branch in my django fork.
This will be the base of my on going work. I also made sure that all tests are
passing, since there were some issues with changes in the
I'd like to see Django become a bit more like Colony [0], maybe spiced
up with a shoot of ZeroMQish behavior and Mongrel2 on top :-)
In my opinion that would be very interesting for you, you could
justify it as being worthy a PhD thesis and a lot of projects in the
FLOSS community could
On Sun, 29 May 2011 15:57:34 +0300, Fraser Nevett
wrote:
On May 29, 5:22 am, Julien Phalip wrote:
As a side thought, if this functionality does get implemented, would
it be feasible/desirable to have Django emit a warning to encourage
the developer to
On Sun, May 22, 2011 at 05:42:00PM -0700, Chris Beaven wrote:
> Isn't the first suggestion (__contains) achievable already by just chaining
> two filters: Group.objects.filter(persons=p1).filter(persons=p2) ?
Sure, but if I want to filter on several different numbers of persons,
it gets very
On May 29, 5:22 am, Julien Phalip wrote:
> I'm bringing this up to the dev-list as I'm keen to hear if someone is
> interested in this problem and has suggestions towards a robust
> solution. It is a pretty serious issue that I hope can be resolved by
> the 1.4 release.
For
On 15.04.2011, at 15:25, Ned Batchelder wrote:
Hi Ned,
> As you say, Jannis has suggested that a Babel-based solution isn't that much
> work. But that work hasn't been done yet. I don't know how much work it is.
> It's going to be a larger change to the code base than my patch is, at least