On Mon, Nov 29, 2010 at 4:32 AM, Christophe Pettus wrote:
> Hi,
>
> I'm updating the patch for #12180 to work with the dev version of 1.3, and
> preparing a test case for it. Being new to the Django test suite, it's not
> clear to me how to introduce a backend-specific and settings-file-specifi
On Sun, Nov 28, 2010 at 11:30 PM, Jacob Kaplan-Moss wrote:
> Hi Russ --
>
> On Sun, Nov 28, 2010 at 1:13 AM, Russell Keith-Magee
> wrote:
>> For your consideration, I present a patch to resolve #12815 and
>> #12816, adding a TemplateResponse and a render() shortcut.
>
> Good stuff.
>
> A couple o
On Mon, Nov 29, 2010 at 4:21 AM, Ivan Sagalaev
wrote:
> On 11/28/2010 10:13 AM, Russell Keith-Magee wrote:
>>
>> For your consideration, I present a patch to resolve #12815 and
>> #12816, adding a TemplateResponse and a render() shortcut.
>
> Thank you!
>
>> - The render() shortcut doesn't use Te
On 11/29/2010 02:58 PM, Russell Keith-Magee wrote:
My counterargument would be this -- if you use TemplateResponse,
there's no need to use a shortcut at all.
Yes, this is what I understood from your reasoning. I'm concerned more
with documentation. Namely, what are we going to suggest for usag
I agree with Jacob on the bake/baked thing.. but maybe it's just
CakePHP coming to haunt me :S
On Nov 29, 1:09 pm, Ivan Sagalaev wrote:
> On 11/29/2010 02:58 PM, Russell Keith-Magee wrote:
>
> > My counterargument would be this -- if you use TemplateResponse,
> > there's no need to use a shortcu
Hi,
Before I put any work into this, I want to know if (a) I'm missing something
super-obvious in the QuerySet functionality, or (b) this idea has already been
explored and rejected.
Sometimes, it would be nice to get a slice of a QuerySet but *not* actually
evaluate the QuerySet; instead, lea
On 11/29/2010 11:31 PM, Christophe Pettus wrote:
Before I put any work into this, I want to know if (a) I'm missing something
super-obvious in the QuerySet functionality, or (b) this idea has already been
explored and rejected.
Hi Christophe,
Looks like you're indeed missing queryset slicing
On Nov 29, 2010, at 12:50 PM, Ivan Sagalaev wrote:
> Looks like you're indeed missing queryset slicing[1]. It is lazy.
>
> [1]:
> http://docs.djangoproject.com/en/dev/topics/db/queries/#limiting-querysets
Bah, I was confusing indexing (not lazy) and slicing (lazy). Never mind, and
thanks. :)
On Fri, Nov 26, 2010 at 8:38 PM, Russell Keith-Magee
wrote:
> Ok - looks like I had a couple of seriously loose screws last night.
> I'll take another look today. Apologies for the confusion.
I noticed that you merged the change in — thanks!
I saw that you explicitly imported the names that used
> Can you be specific on how the current setup is preventing you from
> getting it done?
I think the easiest way is to look at my code on bitbucket, for
example my models.py:
https://bitbucket.org/bolhoed/django_disqus_comments/src/b2c6fbb025f6/models.py.
As you can see, I have to hack my own mod
I'm not going to get into the arguments about security of the various
hashing methods, other than to observe that there have been some
fairly misleading statements here.
As far as the proposal goes, I think this is a perfectly reasonable
feature request (and you should open a ticket about it if on
History: http://code.djangoproject.com/wiki/PylibmcSupport
Draft: https://gist.github.com/91de59e53f7f36f461ec
Caveats/Notes:
A) This is only the memcache.py file, changes to conf/global_settings
and core/cache/base will be needed to handle the move towards
CACHE_SETTINGS
B) pylibmc and memcache
My client is in a immediate need for a front end engineer whi knows
Django, Python, AJAX, and/or html5 . This is a full time position with
a really good pay in Palo Alto, CA. Sent me your updated resume if
interested.
--
You received this message because you are subscribed to the Google Groups
13 matches
Mail list logo
