I tend to agree that #6362 should be reconsidered. Realistically
speaking, almost all form fields aren't going to want leading or
trailing spaces. The default case, therefore, should strip them,
while allowing the app writer to override that behaviour in the small
minority of cases where the whit
On Thu, Jun 3, 2010 at 4:38 AM, Russell Keith-Magee
wrote:
> [...]
> Regarding #13480 specifically -- I haven't dug into the problem in
> detail, but the approach of telling exceptions apart by inspecting the
> number of arguments doesn't fill me with joy. One of the changes in
> 1.2 was to improv
It was suggested in bug #13480 that I raise this issue "during the 1.3
feature discussion phase", which we seem to have entered.
Essentially, the issue is that a typo in my_app/views.py or any of its
dependencies can raise an error on module import and break the entire
site, leaving the user with
I think that http://code.djangoproject.com/ticket/13480 may be
relevant to your interests.
-FM
On Fri, May 28, 2010 at 8:22 AM, Arthur Koziel wrote:
> Hey there,
>
> my name is Arthur Koziel and I'll be working on the app loading refactor for
> this year's gsoc program. I'm currently a business
> That doesn't make any sense since a fixed bug would be closed.
Not until after time is spent trying to reproduce/understand the bug.
If you know when it was last seen, you can confirm that you are
triggering it correctly, but that it no longer exists in the current
version.
>> interpretation, u
My interpretation of the "version" field is "the most recent version
in which the problem has been confirmed". If a user spots something
in an older version, it could be fixed or made irrelevant in SVN,
leading to a search for a problem which doesn't exist. By that
interpretation, updating the ve
My apologies, I did not intend to trigger an offtopic discussion, even
a semi-related one. My intent was merely to point out that Django's
templating system is far from perfect, and that improving it is
definitely a goal of Django, even if we reject a particular change
that may appear to be for th
't know Latex, and I don't really understand the example.
> something about autoescaping?
>
> @Charlie: The bikeshed should be a light blue, with white trimming. I
> kinda assumed the dev's picked modulo (yes, shift 5) since it was one
> of the more obscure buttons.
>
I'm mostly just a user, and maybe I'm being dense, here, but I just
don't see the point of this change. Why is {%%} any harder a syntax
than {{{}}} is? Is it an issue of key placement (% is shift-5 for US
keyboards)? And why would you type {%%} and then go back to insert
the keyword when you can
It seems to me like the biggest problem with a settings module not
importing is that it's not safe to display a full error message about
that file. You can't tell if DEBUG is on, and there may well be
information in the settings that is a Bad Idea to leak on a production
server.
Also, as a friend
10 matches
Mail list logo
