Hi.
Can anyone let me know why XViewMiddleware
(django.middleware.doc.XViewMiddleware) have
dependency on auth subsystems?
I reported this issue, and submitting a patch, but it has been marked "wontfix".
http://code.djangoproject.com/ticket/7299
I think XViewMiddleware does not need auth
On May 23, 2:29 pm, "Gary Wilson Jr." <[EMAIL PROTECTED]> wrote:
> However, one of the benefits of values() returning a dict is that you
> avoid the more expensive model instance creation when you don't need it.
I wouldn't be so quick to assume that creating model instances (or
ducks that look
Nope it's just something I was throwing around.
What would exclude do in that example? I feel it should be explicit rather
than implicit (although I do see the reason for implicit calls where you
don't want to return text/blob fields, but explicit is always better).
On Fri, May 23, 2008 at 3:18
David Cramer wrote:
> IMO show() and hide() are extremely ugly. And I think .values() is becoming
> ugly with the addition of values_tuple or whatever it's called. I don't see
> a real good reason to clutter the namespace even more than it already is.
> I'd rather have .values(type=dict) or
On Fri, 23 May 2008 13:32:45 -0500
"Gary Wilson Jr." <[EMAIL PROTECTED]> wrote:
> In case you haven't figured this out already, it can be done by
> importing your unit test classes from the test/*.py modules in
> tests/__init__.py
That is exactly what I have done at my work, just a few days
IMO show() and hide() are extremely ugly. And I think .values() is becoming
ugly with the addition of values_tuple or whatever it's called. I don't see
a real good reason to clutter the namespace even more than it already is.
I'd rather have .values(type=dict) or something similar.
On Fri, May
Alex Koshelev wrote:
> No. Not `tests.py`, but `tests` module - that can be a package of many
> other modules/files
In case you haven't figured this out already, it can be done by
importing your unit test classes from the test/*.py modules in
tests/__init__.py
Gary
On Sat, 17 May 2008 13:04:36 +0200
Sebastian Bauer <[EMAIL PROTECTED]> wrote:
> Thank you for answer, but for update, i think, is really important
> for commercial projects and places where you need to be sure that no
> one changed row in parallel
I don't think that commercial projects have an
Haroldo Stenger wrote:
> I think I've found a bug in Django and a solution :-)
Please file a ticket [1] (after searching first [2]) for this issue if
you haven't already so that it's not forgotten.
[1] http://code.djangoproject.com/simpleticket
[2] http://code.djangoproject.com/query
Thanks,
I haven't looked at what your doing real close, but it seems to me
your trying to re-implement the shlex module [1] which has been in the
Python standard library since 1.5.2. Will that do the trick?
[1]: http://docs.python.org/lib/module-shlex.html
On Fri, May 23, 2008 at 10:56 AM, akaihola
It's confusing that the django.utils.text.smart_split() function un-
escapes quotes and backslashes inside the literal string while
preserving the surrounding quotes:
>>> print ' '.join(smart_split(ur'arg1 "the \"second\" argument"
"the \\third\\ argument"'))
arg1 "the "second"
Because of I needed the patch more urgent I actually thought by
myself, I have already uploaded a new version including test cases.
I found a bug by the way, that breaks the ability to derive from a not
abstract model, but I have fixed it. If you are already using the
previous version of my
On 23 mayo, 13:00, "Mike Scott" <[EMAIL PROTECTED]> wrote:
>
> Maybe having to state a storage location on a per-row level. (IE this could
> happen by overriding the manager, and simply switching DB at selection time.
> or being able to provide the DB info at selection time.)
Maybe i good thing
On May 22, 6:53 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> Simon Willison wrote:
> > Thankfully Ivan Sagalaev's confusingly named mysql_cluster
>
> BTW does anyone have a suggestion how to rename it? I've picked
> mysql_cluster simply because I didn't know that there exists the thing
> named
You need to be aware that this is quite complicated if your model has
foreign keys in it: if you use the ORM to do queries, the ORM would
have to be so smart as to when to split up your queries instead of
doing joins.
eg you have model A which foreign keys to a User model. For a row of A
that is
On Fri, 23 May 2008 17:20:43 +0800
"Russell Keith-Magee" <[EMAIL PROTECTED]> wrote:
> I'm currently sitting in an airport, so I won't have a chance to have
> a good look until tomorrow at the earliest. However, here's some
> immediate feedback. Most of them are in the category of "this probably
>
The django.utils.text.smart_split() function used to split template
tag contents seems to strip backslashes. On the other hand, string
literals in variables (like {{"mystring"}}) are passed to the filter
expression parser with backslashes intact.
This complicates things a bit. Forget the part
On 22 touko, 18:47, "Nicolas Lara" <[EMAIL PROTECTED]> wrote:
> objet it refers since I dont see any case in which it would make sense
> to have the replies away from the objects being replied upon.
I've experimented with both approaches on a couple of websites, and
the "correct" solution
While I was trying to implement allowing filter expressions as
arguments to some built-in template tags (see #5756), I found
inconsistencies in the handling of literal strings in the template
system.
Collin Grady's patch [1] for {% ifequal %} looks good, but using the
same logic for other tags
On Fri, May 23, 2008 at 2:59 AM, Simon Willison <[EMAIL PROTECTED]>
wrote:
> 1. Replication - being able to send all of my writes to one master
> machine but spread all of my reads over several slave machines.
> Thankfully Ivan Sagalaev's confusingly named mysql_cluster covers this
> problem
> I'm testing on SQLite, and I don't get that failure when running on
> vanilla trunk.
I am sorry. You was right, but I have fixed it.
> > > I just updated to your latest patch and there appears to be 2 test
> > > failures:http://dpaste.com/52137/, the first one appears to be
> > > caused by the
21 matches
Mail list logo