> There's a similar ticket to this at 7154 (http://
> code.djangoproject.com/ticket/7154). It has a patch that works but I
> am not sure if it is the most elegant method.
Whoops! Sounds like we're talking about the same thing. I thought
based on the summary that it was a different problem, bec
On May 17, 5:38 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I've opened up a ticket 7252 [1] with patch, but I'm not sure my patch
> addresses the problem from the right angle, so if someone knows a
> better way to go about fixing it, I'd like to open the discussion here
> for better ways
I've opened up a ticket 7252 [1] with patch, but I'm not sure my patch
addresses the problem from the right angle, so if someone knows a
better way to go about fixing it, I'd like to open the discussion here
for better ways to fix this.
Essentially what's happening is that the manager is being in
But python also PARSES both branches of the given expression, so if
there was a SyntaxError, it would fail as well, the code doesn't get
run, as well as the template don't get rendered.
there are two distinct phases to template evaluation - parsing and
rendering, some tags (load for example) have
could someone tell me when this ticket will be add to trunk:
http://code.djangoproject.com/ticket/2705
its very important to me because im writing game and i need this to finish
Thanks for answer
PS. sorry for my really bad english
--~--~-~--~~~---~--~~
You rec
Howdy --
In python, conditionals only evaluate the appropriate branch and only
after evaluating the condition. We can say:
if 'foo' in bar_dict:
print bar_dict['foo']
else:
print "Foo not in bar"
Even if bar_dict doesn't have a key 'foo' the first branch of the
conditional is not evalua
I have released a new patch. See
http://code.djangoproject.com/attachment/ticket/7210/0001-Added-expression-support-for-QuerySet.update.3.patch.
What I have done since the last version of this patch:
(1) Added F object support to filter and exclude.
(2) Implemented __radd__, __rsub__, __rmul__,
Okay, so I've got some additional information for you which are
hopefully useful for you. I've tried to switch to the dev version but
I don't think that I'm on the right way right now.
So, here the SQL-code which generates the database view:
SELECT tr.*, tp.TestPlanName,
(SELECT IF(COUNT(Produ
+1 on no silent errors by default.
Tying behaviour to the DEBUG setting is wrong: if you're building a
template with optional Titles, you'd want to be able to test it in
your debug environment with Titles both present and missing.
I know creating more syntax is evil, but how about {{ post.title
I've inherited django.contrib.auth.User model
class MyUser(User):
friends = models.ManyToManyField("self", symmetrical = False,
related_name = 'f_set')
objects = UserManager()
class Admin:
pass
Other fields were removed for simplicity.
Now I run shell and
On May 15, 11:36 pm, Luke Plant <[EMAIL PROTECTED]> wrote:
> I've been using twill integrated into Django unit tests (as described
> here:http://www.djangosnippets.org/snippets/665/), but came across
> the problem that exceptions are hidden by Django's exception
> handling, so it's very difficult
We are still interested in providing the adaptor. Look forward to the
'Getting Started'.
Regarding the 'Maintaining problem', this is not a problem as
evidenced by the IBM Rails adaptor project as Rails has progressed
from 1.x to 2.x
On Apr 14, 2:26 pm, Robert <[EMAIL PROTECTED]> wrote:
> If have
HOMEPAGE: http://www.brandedsite.com
CONTACT: [EMAIL PROTECTED]
PAYMENT: Western Union / Bank of china / paypal
We are a proffesional asian wholesaler of --wholesale cheap
Nike Sneakers: Air Force One,Air Jordans1-22,
Jordan2.2,Jordan2.5,3.5,4.5, 6.5,7.5,13.5,15.5,21.5
On May 15, 3:12 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> First off: support for GROUP BY, SUM and other aggregation functions
> is a work in progress. The new QS-RF code contains placeholders to
> hold GROUP BY statements, but there isn't a public API to get a GROUP
> BY into your qu
14 matches
Mail list logo
