On Sat, Nov 14, 2009 at 1:01 PM, Stephen Crosby wrote:
> Thanks for the response Russell,
>
> We can get into exactly what I'm doing if we need to, but for now lets just
> assume that I've thought this through fairly thoroughly and I do in fact
> want to start background
On Fri, Nov 13, 2009 at 11:15 PM, Russell Keith-Magee
wrote:
> On Sat, Nov 14, 2009 at 8:55 AM, Luke Plant wrote:
>> Hi all,
>>
>> The online docs can easily give the impression that we have perfect
>> compatibility with Django 1.0 — the 'Django
On Sat, Nov 14, 2009 at 4:15 AM, stevecrozz wrote:
> I tried to reopen this bug http://code.djangoproject.com/ticket/9286,
> but apparently that's a no-no since it was closed as invalid by a core
> developer.
>
> I'd like someone to take another look at it since I think
On Sat, Nov 14, 2009 at 4:31 AM, Warren Smith wrote:
> On Thu, Nov 12, 2009 at 5:17 PM, Russell Keith-Magee
> wrote:
>>> 1. Retrieve the credentials from the session.
>>> 2. Create a new, or update an existing, entry for those credentials in
>>> the
Could I please get a core committer or a triager to take a look at
this ticket and triage it please? It fixes a fairly core bug in the
db.model.field code:
http://code.djangoproject.com/ticket/11716
What's the right process here, should I move it to 'Accepted' myself?
--
--Leo
--
You received
Hi all,
The online docs can easily give the impression that we have perfect
compatibility with Django 1.0 — the 'Django over time' section on [1]
has a link to 'Backwards-incompatible changes' [2], which contains
pre-1.0 changes only, and a notice at the top saying you don't need to
read it
I'm back at this one since it apparently is around +0 in the voting,
though it still does not have a committer.
I've updated the diff to work against trunk, and fixed some
documentation errors. However, I'm not able to attach a file to the
ticket. I receive this error:
403 Forbidden
I tried to reopen this bug http://code.djangoproject.com/ticket/9286,
but apparently that's a no-no since it was closed as invalid by a core
developer.
I'd like someone to take another look at it since I think Jacob didn't
understand the bug because the original poster's example was
ambiguous. I
On Thu, Nov 12, 2009 at 5:17 PM, Russell Keith-Magee
wrote:
>> 1. Retrieve the credentials from the session.
>> 2. Create a new, or update an existing, entry for those credentials in
>> the database configuration.
>> 3. Somehow ensure that the using() operator is used on
Hey,
a little status update:
We've switched our work to Alex' github multi-db branch because we
depend on that to make a clean non-relational backend API. Otherwise
we'd have to rewrite too much code once multi-db gets merged into
trunk. The new branch is at:
10 matches
Mail list logo