On Fri, Aug 22, 2008 at 4:08 PM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
> 1) You have less than 2 weeks left and still 188 tickets marked with
> 1.0 tag
Correction: we have 153 tickets open with the 1.0 milestone. Not bad
for eight hours' work, IMHO, and we've still got a couple sprints left
to
Matt,
FYI, r8471 fixed my problems and all Oracle GeoDjango tests pass
again. Thanks.
-Justin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
On Fri, 2008-08-22 at 15:53 -0700, mattxbart wrote:
> Has anyone used python-ldap under fastcgi? Through the python
> interpreter I get expected results (con.simple_bind returns
> authenticated status code or throws exception) but when executed
> through the admin web form I get gateway timeouts
Has anyone used python-ldap under fastcgi? Through the python
interpreter I get expected results (con.simple_bind returns
authenticated status code or throws exception) but when executed
through the admin web form I get gateway timeouts under eginx and
500's under lighttpd, both using fastcgi
On Fri, Aug 22, 2008 at 4:08 PM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
> Really?
Dude. Don't be that guy. OK?
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~-~--~~~---~--~~
You received this message because you are
On Fri, Aug 22, 2008 at 10:25 PM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> On Fri, Aug 22, 2008 at 2:26 AM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
>>
>> Hi core devs,
>>
>> could you please force http://code.djangoproject.com/ticket/8367 to
>> include into 1.0 asap?
>
> Please don't do this.
FWIW, I think this is a fairly consistent way that web and application UIs
are designed. Checkboxes normally have their labels to the right. Go to
Tools|Options in Firefox right now, or consider any number of well-designed
web forms. (Kudos to the Django developers for using the label tag, too;
In the admin site, all fields have this kind of placement:
label_a: formfield_a
label_b: formfield_b
but checkboxes are:
formfield_c: label_c
I think introducing this different behaviour only for checkboxes is
aesthetically and logically wrong.
On Fri, Aug 22, 2008 at 9:35 PM, Waylan Limberg
On Fri, Aug 22, 2008 at 1:12 PM, Alex Rades <[EMAIL PROTECTED]> wrote:
>
> Hi,
> Is there a reason for checkboxes (BooleanField) in admin having the
> label on the right side instead of left?
Isn't that how check boxes are generally displayed? I don't recall
them the other way anywhere - and
Hi,
Is there a reason for checkboxes (BooleanField) in admin having the
label on the right side instead of left?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
In case anyone else gave up on the above link,
http://docs.djangoproject.com brought me successfully to
http://docs.djangoproject.com/en/dev/
Can't wait to check out the new docs!
Thanks,
Wayne
On Aug 22, 12:21 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> I've tried several times yesterday and
Try this link instead: http://docs.djangoproject.com/en/dev/
On Aug 22, 12:21 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> I've tried several times yesterday and today to go to the new docs
> link above, but unfortunately 404'ed every time.
> Thanks,
> Wayne
>
> On Aug 19, 6:01 pm, "Jacob
I've tried several times yesterday and today to go to the new docs
link above, but unfortunately 404'ed every time.
Thanks,
Wayne
On Aug 19, 6:01 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> Hi folks --
>
> The docs refactor work is pretty much done; now I need a bunch more
> eyes to
On Fri, Aug 22, 2008 at 2:26 AM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
>
> Hi core devs,
>
> could you please force http://code.djangoproject.com/ticket/8367 to
> include into 1.0 asap?
Please don't do this. The ticket is marked as 1.0 and is accepted. It
will get into 1.0.
--
Brian Rosner
I'd also just like to say thanks, it looks like a tremendous amount of
work, and a big gain for the entire django community!
On Aug 22, 7:03 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Fri, Aug 22, 2008 at 4:12 AM, Nicolas Lara <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I am
On Fri, Aug 22, 2008 at 9:34 AM, Russell Keith-Magee <[EMAIL PROTECTED]
> wrote:
> I suspect that re-ordering the imports at the top of mysql.base will
> fix this problem. Open a ticket and I'll put this on my todo list.
>
>
Done, #8485.
Thanks,
Karen
On Fri, Aug 22, 2008 at 9:07 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> Shouldn't the ImproperlyConfigured form the backend's base.py
> get propogated up so that the real cause of the error (MySQLdb either
> missing or too old) can be seen?
This change certainly wasn't intentional. Looking at
I noticed a thread on the user's list (
http://groups.google.com/group/django-users/browse_thread/thread/c0d55dfea1f2a43c#)
reporting that the result of trying to trying to run with the database
backend set to 'mysql' but no MySQLdb installed is now the simple message:
Error: No module named
Hello,
i'm using the stable version of django (0.96.2).
When the newforms library tries to return a field's validation error,
if the translation contains an accent, it returns me an
UnicodeDecodeError. If i deactivate i18n in settings.py, all runs
correctly (showing the messages in english).
The
Hi core devs,
could you please force http://code.djangoproject.com/ticket/8367 to
include into 1.0 asap?
I was also beaten by it when migrating project with customization of
viewed and edited fields :(
diff --git a/django/contrib/admin/options.py b/django/contrib/admin/options.py
index
Hello,
i'm using the stable version (0.96.2) of Django.
When newforms library try to returns a field's validation error, if
his translation contains any accent, it returns me an
UnicodeDecodeError. If i deactivate i18n in settings.py all runs
correctly (showing the messages in english).
The
On Fri, Aug 22, 2008 at 4:12 AM, Nicolas Lara <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I am writing to let you know that I have posted the latest patches on
> aggregation support. All the planned features are implemented in the
> patch for #3566.
I would just like to take this opportunity to
Thanks for all the great info. Usually articles refer ''.join(...) as
the fastest concat operation, but it won't do type coersion of course.
I was interested whether there was a Django standard for this sort of
thing. In any case the '+' operator is discouraged by all.
Regards,
Joost
Awesome! Simply, awesome! Thanks for all your hard work. I can't
wait to see this in trunk!
-Eric Florenzano
On Aug 21, 1:12 pm, "Nicolas Lara" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am writing to let you know that I have posted the latest patches on
> aggregation support. All the planned
Hi,
Just a short reply here (please repost on django-users, if the answer
is not satisfying :).
First, you are not seeing the problem using MyISAM because MyISAM does
not do any checks of foreign key constraints. To obtain similar
behavior using InnoDB tables you can do the following:
SET
25 matches
Mail list logo
