On 17 maj 2006, at 12.45, Michael Radziej wrote:
> Nicola Larosa (tekNico) wrote:
>
>>> /me makes another note to spend some serious time with BZR...
>>
>> Try spending some time with Mercurial, too. It's simpler, smaller and
>> faster than Bazaar-NG, while also being written in Python, with a
>>
On 18 aug 2006, at 15.07, Malcolm Tredinnick wrote:
>
> On Fri, 2006-08-18 at 05:54 -0700, olive wrote:
>> Hi folks,
>>
>> Have you read the following from Django Comments, what do you
>> think of
>> it ?
>
> This seems to be in response to some question. What is the context,
> though? What was
On 16 nov 2005, at 11.41, Bjørn Stabell wrote:
Is there any work underway to implement more than two-levels of inline
editing in the admin interface? I.e., Company/ Department/ Team/
Person in one interface?
I see this talk about 'new-admin' so I'd thought I'd ask.
What I've gathered from l
dy willing to submit a patch?
http://code.djangoproject.com/ticket/904
- Daniel
--
Daniel Ericsson
http://monowerks.com/ | http://lounging.com/
On 7 dec 2005, at 06.21, Adrian Holovaty wrote:
But my rationale for changing to the magic object approach is: If we
move to class-based lookups (Person.objects.get_list() rather than
people.get_list()), the class will have been imported *anyway*, so
it's not too much of a big deal to have to u
On 7 dec 2005, at 10.53, Daniel Ericsson wrote:
I find the use of "objects" as a way of namespace separation a bit
off-putting. Enforcing an invocation-style via stack inspection
would cut down on the line-noise. Not a terribly big deal, just how
I'd try to do it un
On 13 jan 2006, at 03.32, Adrian Holovaty wrote:
While we're at it, let's rename DjangoContext to something that
reflects the fact that you pass in an HttpRequest object and it has
context processors. RequestContext, SuperContext, FlexContext,
AdvancedContext -- those ideas are all pretty lame.
