On Fri, 2008-02-01 at 20:40 -0600, Tom Tobin wrote:
> On 2/1/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > I'm probably -0 on this. It's a little unnecessary code churn and being
> > able to track what lines changed when is unbelievable handy, so code
> > shuffling should be resisted.
>
I want to starting contributing to Django, and so I tried to create an
account in the ticket system. But I discovered (via the registration
error message) that I already have an account, which I guess I created
it when I first started learning Django. (Why'd I do that? I have no
idea. :-) )
On 2/1/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I'm probably -0 on this. It's a little unnecessary code churn and being
> able to track what lines changed when is unbelievable handy, so code
> shuffling should be resisted.
Copying in subversion retains history; why would we lose
On Fri, 2008-02-01 at 12:47 -0600, Tom Tobin wrote:
> I'm in the midst of resurrecting my "taghelpers" code that makes
> writing complex template tags much easier; as with all my patches, I'm
> using Mercurial to track Django locally while I work on them. Thing
> is, I've moved nearly
On Tue, 2008-01-29 at 14:13 -0600, Jacob Kaplan-Moss wrote:
> Howdy folks --
>
> The short version:
>
> I'd like to deprecate initializing models using positional arguments
> (i.e. ``p = Person(1, 'Joe Somebody')``) in favor of only allowing
> keyword-argument initialization (i.e. ``p =
On Tue, 2008-01-29 at 12:50 -0800, Ivan Illarionov wrote:
> > One of the other things planned as part of qs-rf is the ability to use
> > custom queries to initialize models -- something like
> > ``Model.objects.custom_query("SELECT ...")``
> That's not enough - I need this feature to initialize
On Feb 1, 2008 1:47 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> That said, I'd like to propose that the majority of the contents of
> django.template.__init__ be preemptively moved to
> django.template.main, and imported back into __init__ as necessary.
> Furthermore, I'd like to see all use of
I'm in the midst of resurrecting my "taghelpers" code that makes
writing complex template tags much easier; as with all my patches, I'm
using Mercurial to track Django locally while I work on them. Thing
is, I've moved nearly everything out of django.template.__init__ into
a django.template.main
Hello,
I'm sorry to post it here but I was unable to post it (400 Bad
Request) into:
http://code.djangoproject.com/ticket/2413
Hello,
I run latest SVN but I guess I'm having similar problems:
http://groups.google.com/group/django-users/browse_thread/thread/aa0b83e3aa91fb63
Any hint on this
dan,
i'm currently suffering from this problem too.
did you meanwhile find a usable alternative for validator_list in
newforms-admin?
On 21 Jan., 01:32, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> What about using a ComboField then add the other fields as
> validators., override
Hi,
I'm using newforms-admin branch and I'm having some problems with
ImageField(possibly with FileField too).
When saving a form in the admin and not validates some field the
ImageField shows something like:
Currently: {'content': '', 'content-type': 'image/png', 'filename':
'test.png'}
And on
11 matches
Mail list logo
