I am mrts (Mart Sõmermaa).
The page was created and updated by me and I'm quite certain the
anonymous updates are also mainly by me. So I am entirely to blame for
the confusing naming and for any incorrect information. But I do hope
that the information is mostly correct and relevant, it is just
Greetings all -
Just a quick note to give you the details of the London Sprint
tomorrow:
Address:
57-61 Mortimer Street, London;
Start Time:
10am
To gain access, please call me on 077 6840 1800
Any questions - feel free to email me on this address or call me on
the number above.
See
On Thu, Aug 28, 2008 at 8:18 PM, Rock <[EMAIL PROTECTED]> wrote:
>
> What you are describing is an edge case for the notion of "sharding"
> which is the deployment of identically structured DBs where different
> batches of users get saved in different databases. (Flickr does this.)
You could also
Hi,
I've lost my password on http://code.djangoproject.com, there is a way
to recover/reset it?
Thanks,
Nuno
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send emai
On Fri, Aug 29, 2008 at 7:39 AM, Nuno Mariz <[EMAIL PROTECTED]> wrote:
> I've lost my password on http://code.djangoproject.com, there is a way
> to recover/reset it?
http://www.djangoproject.com/accounts/password/reset/
Jacob
--~--~-~--~~~---~--~~
You received t
On Aug 29, 2:23 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> http://www.djangoproject.com/accounts/password/reset/
>
> Jacob
Thanks Jacob,
The http://www.djangoproject.com/password_change/ link sent in the
email is broken.
Nuno
--~--~-~--~~~---~--~~
You r
On Fri, Aug 29, 2008 at 8:36 AM, Nuno Mariz <[EMAIL PROTECTED]> wrote:
> The http://www.djangoproject.com/password_change/ link sent in the
> email is broken.
http://www.djangoproject.com/accounts/password/change/
Jacob
--~--~-~--~~~---~--~~
You received this mes
Hi folks --
While working on some URL-related issues, I ran across a pretty big
problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into
the templates: if it does that, there's no way to have "optional"
links. The perfect example is #7810 and the admin docs: if the URLs
for the adm
Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit :
>
> Hi folks --
>
> While working on some URL-related issues, I ran across a pretty big
> problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into
> the templates: if it does that, there's no way to have "optional"
> links. The pe
On Fri, Aug 29, 2008 at 12:43 PM, David Larlet <[EMAIL PROTECTED]> wrote:
>
>
> Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit :
>
>>
>> Hi folks --
>>
>> While working on some URL-related issues, I ran across a pretty big
>> problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into
I have 2 querysets q1 and q2.
I want q3 = q2-q1, where q3 is a queryset object and contains only the
objects in q2 that are not in q1.
Is there built in support for this operation?
The only thing I can think to do is:
list( set(q2) - set(q1) )
It doesn't return a queryset, but I can deal with i
On Fri, 2008-08-29 at 10:51 -0700, ryan wrote:
> I have 2 querysets q1 and q2.
>
> I want q3 = q2-q1, where q3 is a queryset object and contains only the
> objects in q2 that are not in q1.
>
> Is there built in support for this operation?
>
> The only thing I can think to do is:
> list( set(q
And because I wasn't concentrating about which list I was reading, here
comes the obligatory statement:
Please take any follow-ups to django-users. This mailing list is
for the internal development of Django itself. "How to use"
questions should go to the django-users mail
Am 29.08.2008 um 17:18 schrieb Jacob Kaplan-Moss:
> Are there any objections to me
> sneaking this into 1.0?
Hell, no! That's perfect and also works with blocktrans.
..and let's us kill that captureas in Pinax, yay!
Cheers,
Jannis
--~--~-~--~~~---~--~~
You re
If you want a response, you will need to ask this on the django-users
list. This list is for the discussion of developing the Django
framework itself.
On Aug 28, 2008, at 3:23 AM, Puzzle Stone wrote:
> Fcgi and scgi work well in my machine when i use django0.96.2, but
> scgi failed when I t
hi,all
I use django beta2 and find that model's charfield doesn't require
max_length parameter anymore. Is there any thing wrong?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
I'm mostly through with a drop-in replacement for the old comments, using
the new Comment system and signals. It should be slick.
When it tests out, I'll also commit the new save() parameters mentioned in
the backwards-incompatible page, and we should be again compatible with the
latest Django tr
17 matches
Mail list logo