Umm... How about now? I've been bitten by trailing/leading blank spaces in
form inputs several times now, and I'm tired of monkey patching django to
fix this. Thanks.
Ryan
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this
Hi Paul,
Is it correct that nametuple construction is much slower than for
normal ones or is this true only in older python versions?
On Mon, Jul 4, 2011 at 1:47 AM, paulpmillr wrote:
> Hello.
>
> I've added an implementation for named tuples query set, see
>
On Monday, July 4, 2011 1:42:37 AM UTC+12, brocaar wrote:
>
> What about not implementing this as a url tag but as a translation-
> override tag? Then it is not only possible to specify the language to
> use for your URL translation, but as well for other translatable
> content. Example:
>
>
Hello.
I've added an implementation for named tuples query set, see
https://code.djangoproject.com/ticket/15648
- Named tuples could be iterated over with order saving (like lists /
tuples).
- Properties there could be accessed with dot notation - post.topic
(almost like dicts).
- They could be
>
> I believe as a general principle that a testing framework should always
> return the system under test to the state it was in prior to the run.
> Calling cache.flush() violates that principle -- and of principle concern to
> me, it flushes your *entire* cache. That means if someone executed
I think {% transurl account:register %} would be more convenient to work
with i18n_patterns
On 3 July 2011 10:42, brocaar wrote:
> What about not implementing this as a url tag but as a translation-
> override tag? Then it is not only possible to specify the language to
> use
What about not implementing this as a url tag but as a translation-
override tag? Then it is not only possible to specify the language to
use for your URL translation, but as well for other translatable
content. Example:
{% transoverride language_code %}
{% trans "Register account"