Sorry my mistake. It means white spaces character not spaces
2018년 6월 6일 수요일 오후 6시 3분 48초 UTC+9, Florian Apolloner 님의 말:
>
>
>
> On Tuesday, June 5, 2018 at 4:30:03 AM UTC+2, oli...@kidsnote.com wrote:
>>
>> allowing spaces can be done by simply adding \s* after (arg_sep)s
>>
>
> \s is __not__ th
filter_raw_string = r"""
^(?P%(constant)s)|
^(?P[%(var_chars)s]+|%(num)s)|
(?:\s*%(filter_sep)s\s*
(?P\w+)
(?:%(arg_sep)s
(?:
(?P%(constant)s)|
(?P[%(var_chars)s]+|%(num)s)
)
)?
)""" % {
'constant': constant_string
filter_raw_string = r"""
^(?P%(constant)s)|
^(?P[%(var_chars)s]+|%(num)s)|
(?:\s*%(filter_sep)s\s*
(?P\w+)
(?:%(arg_sep)s
(?:
(?P%(constant)s)|
(?P[%(var_chars)s]+|%(num)s)
)
)?
)""" % {
'constant': constant_string
Currently, spaces between filter separator( | ) and filter name is allowed.
Also, value name and filter separator.
So, following is allowed.
{{ value|filter:"arg" }}
{{ value|filter:"arg" }}
But, following is not allowed.
{{ value|filter: "arg" }}
users are confused by the
2018년 6월 5일 화요일 오전 10시 52분 16초 UTC+9, oli...@kidsnote.com 님의 말:
>
> Currently, django template system allow spaces between filter separator
> and filter name, also value name and filter separator.
> So, following is ok.
>
> {{ value|filter:"arg" }}
> {{ value|filter:"arg" }}
>
>
Currently, django template system allow spaces between filter separator and
filter name, also value name and filter separator.
So, following is ok.
{{ value|filter:"arg" }}
{{ value|filter:"arg" }}
But, following can't be parsed
{{ value|filter: "arg" }}
I think that this
Thank you for your reply.
I understand your opinion well
2018년 5월 31일 목요일 오전 11시 41분 22초 UTC+9, oli...@kidsnote.com 님의 말:
>
> In the template filter system now,
>
> spaces between augment separator and augments generate error.
> For example, the following template code generates the following erro
Are there any reasons that not allow spaces between separator and arg?
2018년 5월 31일 목요일 오전 11시 41분 22초 UTC+9, oli...@kidsnote.com 님의 말:
>
> In the template filter system now,
>
> spaces between augment separator and augments generate error.
> For example, the following template code generates the
In the template filter system now,
spaces between augment separator and augments generate error.
For example, the following template code generates the following error.
{{ value | filter: "arg"}}
TemplateSyntaxError at /
Could not parse the remainder: ': "arg"' from 'value | filter: "arg"'
ht
I should clarify, this is only an issue when wanting to put data *both* in
the query string and the request body.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/dja
;m having trouble following, #11371 (a bit of a brain overload
today).
Is this really intended behaviour?
—Oliver
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.co
0 Mar, 00:33, Russ Amos wrote:
> Oliver, examining unique and unique_together attributes is exactly what I
> have in mind for attempting to follow relationships when deserializing. I
> realize it needs to be dealt with carefully in the inner workings of Django,
> to provide consistency, b
> There should be no monkey-patching involved. Using a separate settings
> file for tests so that it points to its own cache isn't monkey patching
> -- it's normal practice. Tests don't run in production environments, so
> some settings have to be changed.
I do have separate settings for all the
I figured that might be the case. I am wrapping the backend now in
tests, I just hate monkey patching :)
Anyway, thanks for answering, I'm glad it got a definite response.
On Mar 30, 1:01 am, Malcolm Tredinnick
wrote:
> On Sun, 2009-03-29 at 16:28 -0700, Oliver Beattie wrote:
> >
d from the cache in the test cleanup.
Anyway, I just want to poll opinion and gather thoughts to see if
anyone else thinks this may be vaguely useful before opening a ticket
which would likely get promptly closed if nobody else wants it =)
—Oliver
--~--~-~--~~~---~--
I'll admit that I haven't read your whole post (sorry), but one part
caught my eye… the bit about storing relationships not just as primary
keys. If I am right in thinking that you are wanting to do some sort
of "relationship following" I think I can probably help by providing
some initial (but a
Hi django folks,The company I work for has been using django for a few
months now, and I have to say it's a fantastic bit of work. Nice to
finally use a web framework with a decent architecture. Thanks!We've been plagued by one issue that is pretty disturbing, though:
http://code.djangoproject.com/
17 matches
Mail list logo
