On Thu, Jan 13, 2011 at 10:40 AM, Richard Laager wrote:
> On Wed, 2011-01-12 at 21:26 +0800, Russell Keith-Magee wrote:
>> Until I start seeing kibibyte being used in the New York Times, or the
>> prefered usage in the Chicago Manual of Style, the kibibyte is little
>> more to me than an intriguin
On Wed, 2011-01-12 at 21:26 +0800, Russell Keith-Magee wrote:
> Until I start seeing kibibyte being used in the New York Times, or the
> prefered usage in the Chicago Manual of Style, the kibibyte is little
> more to me than an intriguing expression of pedantry. Yes, the
> existing usage is confusi
Don Spaulding ha scritto:
On Jan 12, 4:23 pm, Tai Lee wrote:
On Jan 13, 5:06 am, Don Spaulding wrote:
I will say that the debug template has been
"relying on the bug" since 2005. By my estimation, that makes nearly
every template ever created a candidate for relying on the old
beh
Bah. Premature send. That was supposed to say:
On Jan 12, 6:08 pm, Don Spaulding wrote:
> On Jan 12, 4:23 pm, Tai Lee wrote:
> > On Jan 13, 5:06 am, Don Spaulding wrote:
>
> > This feels too magical to me, and it still leaves the possibility for
> > ambiguous behaviour as you note. Without kn
On Jan 12, 4:23 pm, Tai Lee wrote:
> On Jan 13, 5:06 am, Don Spaulding wrote:
>
>
>
> > I will say that the debug template has been
> > "relying on the bug" since 2005. By my estimation, that makes nearly
> > every template ever created a candidate for relying on the old
> > behavior.
>
> Not
On Wed, 2011-01-12 at 10:06 -0800, Don Spaulding wrote:
> The use case Tai linked was the first (and really, only) bug I ran
> into when porting to SVN trunk. I understand the "usable for
> designers" mantra, and I don't pretend that 'mycallable.func_name' is
> elegant, but frankly, I don't care.
On 12/01/11 17:54, Daniel Swarbrick wrote:
> Most of the time, I use POST for forms, but using GET is useful when
> developing a search form, for example. This is especially true if you
> want to paginate your results, because you still have all your
> original form variables in the query string.
>
On Jan 13, 5:06 am, Don Spaulding wrote:
>
> I can't speak to the number of templates actually in the wild that
> rely on the old behavior. I will say that the debug template has been
> "relying on the bug" since 2005. By my estimation, that makes nearly
> every template ever created a candida
On Jan 11, 8:31 pm, Luke Plant wrote:
>
> So we then have to think about what is sensible behaviour, and I think
> the new behaviour is much simpler and saner, and much more consistent
> with itself.
I agree.
> Also, given the nature of the Django's template system
> (i.e. usable for designers
Most of the time, I use POST for forms, but using GET is useful when
developing a search form, for example. This is especially true if you
want to paginate your results, because you still have all your
original form variables in the query string.
CBV FormView get_form_kwargs() only populates form_
On Mon, Jan 10, 2011 at 7:12 PM, Klaas van Schelven
wrote:
>
> Input (discussion) on this is much appreciated. I'll gladly put in a
> new patch once a decision is reached. If this is a separate issue, I'm
> also fine on opening a separate ticket. (it could be argued that we
> can move forward on
On 12 Gen, 14:26, Russell Keith-Magee wrote:
> You won't see me disagreeing. +1 to keeping as is.
> Until I start seeing kibibyte being used in the New York Times, or the
> prefered usage in the Chicago Manual of Style, the kibibyte is little
> more to me than an intriguing expression of pedantry
On Wed, Jan 12, 2011 at 8:35 PM, Gabriel Hurley wrote:
> Though technically accurate, I would say it goes against the rest of the
> purpose of that filter: "human readable".
> And though technically inaccurate, everyone from hard drive manufacturers to
> major web companies use KB, MB, etc. to rep
On Tue, 2011-01-11 at 20:19 -0800, Tai Lee wrote:
> If we can, I would be in favour of treating the old behaviour as a bug
> and not having to support it while it follows a deprecation path.
>
> However, either way, if the new behaviour stays (and I definitely
> think it should) I think we should
Though technically accurate, I would say it goes against the rest of the
purpose of that filter: "human readable".
And though technically inaccurate, everyone from hard drive manufacturers to
major web companies use KB, MB, etc. to represent filesizes. I'd argue that
it's become a de facto (if
Not a big issue, I know... but aren't we perfectionist? :-)
Looking here:
http://code.djangoproject.com/browser/django/trunk/django/template/defaultfilters.py#L794
and here:
http://en.wikipedia.org/wiki/Kibibyte
I see that a more correct value should be 1000 or more correct labels
should be KiB
16 matches
Mail list logo
