The problem is that the intent is a test like
"bar" in "foo bar baz"
which is true; unfortunately, so is
"bar" in "disbarment"
which shouldn't be (in this context anyway). Thus you should test
"bar" in ("foo","bar","baz")
instead, which seems to be the intent behind this change
IMHo it makes sense to usee a tuple there. I'd go so far as to
recommend *not* to concatenate that (three lines down...); the
subsequent test in line 81 will cause false positives otherwise.
--~--~-~--~~~---~--~~
You received this message because you are
Hi,
On Nov 10, 3:18 am, Arnold Chen <[EMAIL PROTECTED]> wrote:
> Sorry, there is a typo mistake, my question is "how to get logged-in"
> user WITHOUT request parameter.
> Because i want to use it in a function in models.py
There is a clean separation of "what data do you have" and "what data
I've been hacking on django-multilingual a bit in the last few days.
Fixes, so far:
* import it into git (OK, that's not a fix per se, but how would I
work on it otherwise?)
* language codes in the database instead of in settings.py. Yay!
* allow "unique" constraints in translated fields (they
4 matches
Mail list logo
