On Tue, Jun 4, 2013 at 1:48 AM, Anssi Kääriäinen
wrote:
> As for .get() - I don't find the number of duplicates in the error
> message that useful.
Yeah, I'd agree with that. It's another one of those things that goes
WAY back into the misty reaches of Django's history, but I don't think
there's
I'd be inclined to agree with Anssi that we could do something like LIMIT
21 to just remove the issues with large numbers. I have found it quite
helpful to have the exact number when it's small - especially when
debugging issues with strange joins etc.
On 4 June 2013 15:02, Jacob Kaplan-Moss wro
On Mon, Jun 3, 2013 at 7:03 PM, Shai Berger wrote:
> > {% with my_bonnet.bees as bees if my_bonnet.bees %}
> > {% if my_bonnet.bees with my_bonnet.bees as bees %}
>
> The only problem I see with these is the repetition -- we could just allow
> "as" on {% if %}:
>
> {% if my_bonnet.bees as bees %}
On Tue, Jun 4, 2013, Andre Terra wrote:
>I'm mostly concerned with ambiguous behaviour for the clauses which include
>other operands. For example,
Looking at the various solutions that have been proposed, I am not at all sure
that this is something that the template author should have to deal w
If you're posting to this list by logging in to https://groups.google.com/
rather than via email, I'd like to propose that you write your reply above
the quoted message to which you're replying. If you do this, the digest
emails that most subscribers get will be easily previewable from their
em
On Jun 4, 2013, at 1:14 PM, Yo-Yo Ma wrote:
> If you're posting to this list by logging in to https://groups.google.com/
> rather than via email, I'd like to propose that you write your reply above
> the quoted message to which you're replying. If you do this, the digest
> emails that most su
I think I just posted a quick reply and I wasn't sure whether to quote
above or below, but from now on I'll be glad to post in the way that
provides easier readability for everyone.
For long proposals, I'll keep replying below quotes for exactly the same
reason.
On Tue, Jun 4, 2013 at 2:18 PM, Do
On Tue, Jun 4, 2013 at 5:14 PM, Yo-Yo Ma wrote:
> Thoughts?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
Javier
--
You received this message because you are subs
Certainly, when a user is replying to portions of a quoted text separately
(as Russel often does) it is helpful to break up the quoted text into
actionable sections and reply below each. However, when a user is simply
clicking the "Post Reply" button, chances are, it's going to be easier to
rea
Really what you are proposing is an extension of the scope #19353, and I do
feel that if the built in forms are to be made more usable with custom
users, then both the hardcoding of auth.User and the username field should
be addressed together.
One thing not addressed in your authtools approach
On Tue, Jun 4, 2013, Yo-Yo Ma wrote:
>If you're posting to this list by logging in to https://groups.google.com/
>rather than via email, I'd like to propose that you write your reply above
>the quoted message to which you're replying.
I think that would be a bad idea.
>The way it stands now,
On Tue, Jun 4, 2013 at 1:14 PM, Yo-Yo Ma wrote:
> Thoughts?
>
> I think we should all continue to write messages the way we deem best on
an email by email basis. The content of the message is more important than
whether we reply above or below and it's basically impossible for everyone
to consist
On 4 Jun 2013, at 12:00 PM, Daniele Procida wrote:
> * quote what needs to be quoted for context
> * don't quote anything that doesn't need to be quoted
This is, I think, the most useful/important point. There's no need to include a
whole string of previous messages in later ones; this isn't 198
Can we PLEASE not have this argument? It's literally as old as email
itself, and totally futile.
Drop it. Now.
Jacob
On Tue, Jun 4, 2013 at 2:33 PM, Wim Lewis wrote:
>
> On 4 Jun 2013, at 12:00 PM, Daniele Procida wrote:
>> * quote what needs to be quoted for context
>> * don't quote anything t
On Tuesday 04 June 2013, Daniele Procida wrote:
>
> [...] the {% with expensive.method as variable %} way of doing things
> already exists, [...] What about my earlier suggestion that this be dealt
> with in Python, not in templates [...]
This thread, from its start, has mixed two separate (thoug
15 matches
Mail list logo
