Hi,
On 13 Feb., 13:58, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> > On 12 Feb., 16:57, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > > On 2/12/08, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
>
> > > > Hi,
> > > > since Trac does neither allow me to post anonymously nor do I get a
> > > > registra
On Thu, 2008-02-14 at 18:14 +1100, Malcolm Tredinnick wrote:
[...]
> Any strong objections to not behaving like Python here?
Oh, bother. Darn double-negatives. Remove the 'not'. Sentence makes more
sense, then.
Malcolm
--
Honk if you love peace and quiet.
http://www.pointy-stick.com/blog/
There's a bunch of code in ModelForms.__new__ that tries to protect
people from themselves for what looks like a real edge case.
In normal Python code, if you have a class that subclasses from multiple
parents and you try to access an attribute on a parent, Python just
picks the first occurrence
Malcolm Tredinnick wrote:
> On Wed, 2008-02-13 at 21:14 -0500, Josh Hayes-Sheen wrote:
>
>> I was wondering if there was a reason the SQL Index Creation code is
>> located in core/management/sql.py instead of the db backends? Indexing
>> is pretty common but not part of the SQL Standard afaik
On Wed, 2008-02-13 at 21:14 -0500, Josh Hayes-Sheen wrote:
> I was wondering if there was a reason the SQL Index Creation code is
> located in core/management/sql.py instead of the db backends? Indexing
> is pretty common but not part of the SQL Standard afaik,
Well, not part of the formal sta
I was wondering if there was a reason the SQL Index Creation code is
located in core/management/sql.py instead of the db backends? Indexing
is pretty common but not part of the SQL Standard afaik, and this seems
like it reduces flexibility and prevents advanced indexing from being
performed or
On Feb 14, 2008 9:39 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Feb 13, 2008 6:50 PM, Michael Newman <[EMAIL PROTECTED]> wrote:
>
> Hmm, that ticket (6083) specifies a version of "SVN", therefore it wasn't
> included in the sweep of marking newforms-admin tickets as either blocking
> merge o
Django-fan said the following:
> Is there a way in Django to generate webforms from a simple Database
> table so that we can "submit" the user inputs to update a database
> table. In other words, I would like to create a webform on an existing
> database table.
Questions of this nature should be
Hi All,
Is there a way in Django to generate webforms from a simple Database
table so that we can "submit" the user inputs to update a database
table. In other words, I would like to create a webform on an existing
database table.
Thanks in advance,
--~--~-~--~~~---~-
On Feb 13, 2008 7:39 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> As for that other ticket, you could return it yourself as a dup of the one
> that is still open for the problem. Just fill in some settings here:
> http://code.djangoproject.com/settings so you don't show up as
> "Anonymous". Bet
On Feb 13, 2008 6:50 PM, Michael Newman <[EMAIL PROTECTED]> wrote:
>
> Thanks for passing that link along. Worse part is that I seriously
> managed to almost duplicate that patch verbatim in the last 12 hours.
> Shouldn't this be marked as a block to the trunk merge? When I didn't
> see it there I
On Feb 14, 7:10 am, Collin Grady <[EMAIL PROTECTED]> wrote:
> Rock said the following:
>
> > Some thoughts:
>
> > Inplementing form.as_items returning a list of form lines would be
> > nice.
> > This allows a variety of custom formatting options. Examples:
>
> >
> > {% for item in forms.as_items
Thanks for passing that link along. Worse part is that I seriously
managed to almost duplicate that patch verbatim in the last 12 hours.
Shouldn't this be marked as a block to the trunk merge? When I didn't
see it there I thought that I had to have been going crazy.
This ticket is a duplicate of
On Feb 13, 2008 2:57 PM, Michael Newman <[EMAIL PROTECTED]> wrote:
>
> I hit a little problem last night with registering a new user in the
> newforms admin branch. I posted my original question on django-users:
>
> https://groups.google.com/group/django-users/browse_thread/thread/47b6fdc09d9de07c
Rock said the following:
> Some thoughts:
>
> Inplementing form.as_items returning a list of form lines would be
> nice.
> This allows a variety of custom formatting options. Examples:
>
>
> {% for item in forms.as_items }}{{ item }} , {% endfor %}
> <...submit directive...>
>
>
>
> {{ item[
I hit a little problem last night with registering a new user in the
newforms admin branch. I posted my original question on django-users:
https://groups.google.com/group/django-users/browse_thread/thread/47b6fdc09d9de07c
. Working backwards throughout the day, I noticed that
django.contrib.auth.f
Some thoughts:
Inplementing form.as_items returning a list of form lines would be
nice.
This allows a variety of custom formatting options. Examples:
{% for item in forms.as_items }}{{ item }} , {% endfor %}
<...submit directive...>
{{ item[0] }} -- {{ item[1] }} -- {{ item[2] }}
{{ item[3]
While I understand the intent, and I agree that people need to realize
that trunk is quite stable, I don't think this is a good way to go
about it. It seems to me that it will only raise questions about the
Django release schedule: "Wait, if there have been 2297 commits since
0.96, why hasn't ther
Very often I hear people discouraging the use of Django because the
latest version is 0.96 and has been there for quite long (almost an
year, I guess). Many corporates too do not favour software that is a
pre-1.0 version (though their generalization does not hold true for
Django :)
I want to prop
On Feb 13, 2008 2:38 AM, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
>
> On 12 Feb., 16:57, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > On 2/12/08, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > > since Trac does neither allow me to post anonymously nor do I get a
> > > registrat
Further to this I'd like to point out that SQL lite is a very limited
database in respect to the other offerings.
Encouraging such a practice, in my opinion, is a really bad idea.
Just my 2c.
Mike
On Feb 13, 2008 3:55 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On Feb 13, 2008 1:5
21 matches
Mail list logo
