On 8/18/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> On 8/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> >
> > I'd like to suggest a (somewhat controversial) extension:
> >
> > Let any (installed) app provide its own manage.py actions in a similar
> > way -- something like::
>
> FYI
On 8/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> I don't understand this change completely yet, so I can't see the fix
> you might intend. Short version, it doesn't seem to work for default
> commands. The obvious example being that the tests break. call_command()
> in __init__.py cal
On Aug 17, 2007, at 9:09 PM, Deryck Hodge wrote:
>
>
>
> On Aug 17, 2007, at 10:37 PM, Sean Perry <[EMAIL PROTECTED]> wrote:
>
>>
>> On Aug 17, 2007, at 6:49 PM, Russell Keith-Magee wrote:
>>>
>>> At the very least, your patch would need to catch the inevitable
>>> error. Better yet would be an a
Russ,
On Fri, 2007-08-17 at 23:51 -0500, [EMAIL PROTECTED] wrote:
> Author: russellm
> Date: 2007-08-17 23:51:51 -0500 (Fri, 17 Aug 2007)
> New Revision: 5923
>
> Modified:
>django/trunk/django/core/management/__init__.py
> Log:
> Added the ability for end users to register commands with man
On 8/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> I'd like to suggest a (somewhat controversial) extension:
>
> Let any (installed) app provide its own manage.py actions in a similar
> way -- something like::
FYI - I've committed this feature in [5923].
Yours,
Russ Magee %-)
--~--~--
FWIW, easier to use 'svnversion' command than 'svn info' and parsing
result.
On Aug 18, 5:45 am, "Deryck Hodge" <[EMAIL PROTECTED]> wrote:
> Hi, all.
>
> Reading the Django users list, I saw someone mention not knowing what
> the "pre" meant in the version string returned by django-admin.py.
> Th
Deryck Hodge said the following:
> Certain (older?) versions of the entries file are XML. We would need
> to figure out how many versions there are, which doesn't do much for
> future proofing us.
Perhaps only fall back to the client if the 4th line isn't a rev #?
--
Collin Grady
Appearan
On Aug 17, 2007, at 10:37 PM, Sean Perry <[EMAIL PROTECTED]> wrote:
>
> On Aug 17, 2007, at 6:49 PM, Russell Keith-Magee wrote:
>>
>> At the very least, your patch would need to catch the inevitable
>> error. Better yet would be an approach that doesn't require an
>> external call. Is there any
On Sat, 2007-08-18 at 09:22 +0800, !张沈鹏(电子科大 08年毕业) wrote:
> Look at this ,
>
> http://www.djangosnippets.org/snippets/373/
>
> that why I think below code is useful
>
> mytags.py:
> .
> @register.inclusion_tag('xxx.html')
> def page_link(url_name):
>return {"url_name":url_name}
> _
On Aug 17, 2007, at 6:49 PM, Russell Keith-Magee wrote:
>
> At the very least, your patch would need to catch the inevitable
> error. Better yet would be an approach that doesn't require an
> external call. Is there any other data source we can farm? Is there
> anything we can easily glean from th
On Aug 17, 2007, at 8:49 PM, "Russell Keith-Magee" <[EMAIL PROTECTED]
> wrote:
>
> On 8/18/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>>
>> On 8/17/07, James Bennett <[EMAIL PROTECTED]> wrote:
>>> What does this accomplish that 'svn info' doesn't?
>>>
>>
>> Well, nothing, really. :-)
>
> I'm
On Aug 17, 2007, at 8:49 PM, "Russell Keith-Magee" <[EMAIL PROTECTED]
> wrote:
>
> On 8/18/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>>
>> On 8/17/07, James Bennett <[EMAIL PROTECTED]> wrote:
>>> What does this accomplish that 'svn info' doesn't?
>>>
>>
>> Well, nothing, really. :-)
>
> I'm
On 8/18/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
> On 8/17/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > What does this accomplish that 'svn info' doesn't?
> >
>
> Well, nothing, really. :-)
I'm with Deryck - In reality, it achieves nothing that can't be done
easier with svn info, but I'
Look at this ,
http://www.djangosnippets.org/snippets/373/
that why I think below code is useful
mytags.py:
.
@register.inclusion_tag('xxx.html')
def page_link(url_name):
return {"url_name":url_name}
__
xxx.html:
1
2007/8/16, !张沈鹏(电
On 8/17/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/17/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> > So instead of 0.97-pre the version would be 0.97-pre-SVN-5919. This
> > might help make it easier to track down what revision people are
> > running since so many of us run off trunk.
I tried to find out for what queryset_add (http://
code.djangoproject.com/browser/django/branches/newforms-admin/django/
contrib/admin/options.py#L289) is used for. But it seems as if it is
not used in the admin app (besides of defining it).
So for what (is it|should it be) used?
Thx Florian
-
On 8/17/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> So instead of 0.97-pre the version would be 0.97-pre-SVN-5919. This
> might help make it easier to track down what revision people are
> running since so many of us run off trunk. This, of course, would
> have no impact on official releases.
On 8/17/07, Dave Rowe <[EMAIL PROTECTED]> wrote:
>
> Are these people always pulling from SVN? Otherwise, it'd always show
> SVN-Unknown, right? Especially if 'svn' isn't in the path.
>
My assumption is that, yes, the majority of users on a "pre" release
are running from SVN. Is there any oth
On Fri, 17 Aug 2007 14:45:01 -0500, "Deryck Hodge" <[EMAIL PROTECTED]> wrote:
>
> Hi, all.
>
> Reading the Django users list, I saw someone mention not knowing what
> the "pre" meant in the version string returned by django-admin.py.
> This made me think of version numbers more generally, and
Hi, all.
Reading the Django users list, I saw someone mention not knowing what
the "pre" meant in the version string returned by django-admin.py.
This made me think of version numbers more generally, and I wondered
if others saw value in appending an SVN revision identifier on the
version string.
On Aug 17, 12:16 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> And I just realized I missed #3134, which argued for a slightly
> different solution, in the form of an 'order_by' parameter to the
> views.
>
> Personally, I think it's easier to just skip the parameter and rely on
> the fact that
On Jul 16, 4:19 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On 7/16/07, David Cramer <[EMAIL PROTECTED]> wrote:
> > Is there a specific reason that myfield=Nonedoesn't translate to
> > myfield__isnull=True in the database backend?
>
> The reason is in the implementation details, but, come t
On 8/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> My preference would be to make a new ticket and reference the other
> ones. The advantage of this is that it keeps comments and retries
> concerning your patch easy to read and not tangled up with comments
> about the original ticket(s).
2007/8/13, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
> I added code for forms to TemplateResponder (create_form,
> update_form), an example that shows how to use this code and another
> example that shows how to specify the data format at the end of your
> URLs.
I didn't know the curry function, v
2007/8/12, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 8/11/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > Here is my suggestion: the current forms from model or instance are
> > great but you often need a custom form, what about an extra-argument
> > to the collection (better because I alrea
On Fri, 2007-08-17 at 09:32 +, james_027 wrote:
> hi,
>
> while doing some experiment with ModelChoiceField, and having success
> with this settings ModelChoiceField(Item.objects.all(),
> widget=TextInput). There's one thing that didn't work right for me ...
> If I have Item.objects.filter(na
hi,
while doing some experiment with ModelChoiceField, and having success
with this settings ModelChoiceField(Item.objects.all(),
widget=TextInput). There's one thing that didn't work right for me ...
If I have Item.objects.filter(name__icontains=='sony') instead of
Item.objects.all() and the inp
27 matches
Mail list logo
