urce as a hobby. I would just like
to make sure that at the next bug-squashing session by a developer with
commit rights, this patch is checked in.
Thank you,
j
On 4/23/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
>
> On 4/23/07, Joseph Perla <[EMAIL PROTECTED]> wrote:
Ping: simple, ready ticket #3182 is at 4 months and counting:
http://code.djangoproject.com/ticket/3182 . Thank you,
j
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
+1. Follows DRY. An AutoDateTimeField is very common.
j
On 4/6/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
>
> > seems like it should be as easy as a function in contrib somewhere:
> [snip]
>
> Another option is a trivial field subclass::
>
> class AutoDateTimeField(models.DateTimeFie
ne through, then others also were floating stagnant.
j
On 3/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2007-03-06 at 17:39 -0500, Joseph Perla wrote:
> > They don't need to be in 0.96, but can someone at least check in the
> > tickets already
They don't need to be in 0.96, but can someone at least check in the tickets
already decided as ready for check-in?
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&stage=Ready+for+checkin
Some of these have been complete and ready for 2 months.
j
On 3/6/07, Simon G.
Along the lines of get_or_create(), does it make sense to implement a
get_or_set() function for quick caches?
It can be used in this way:
from django.core.cache import cache
...
big_list = cache.get_or_set('big_list', lambda: BigItems.objects.all(),
60 * 60)
to retrieve from cache or
Have you already decided on a simple, fast, non-deprecated, standard way of
extending the User model?
Last I remember, a ForeignKey(unique=True) was recommended, but that was
kind of a hack due to the deprecation of the OneToOneField.
j
--~--~-~--~~~---~--~~
You re
self or this or whatever it is in python/djangomanagers
code. I'm also not sure how to do the crazy **kwargs stuff. The rest is
clear: if you didn't create it, just update it, save it, and return.
j
On 12/20/06, Joseph Perla <[EMAIL PROTECTED]> wrote:
There should also b
There should also be an update_or_create() function. I often find myself
get_or_creating, then updating the object's dict if it wasnt just created,
then saving. This can easily be expressed more clearly in one line with
this function.
j
On 12/20/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
Smi
