Re: Ad-hoc Django integration for fault-tolerance

For those wondering -- I've found out the cause. Google stopped sending notifications about messages to django-dev awaiting moderation, so there was a backlog of messages that needed to be moderated. Karen Tracey discovered the backlog this morning, and approved the messages; hence the flood.

Re: Ad-hoc Django integration for fault-tolerance

I also got the backlog, in addition my gmail has been buggy and slow for a few days, so I'm assuming it's Google having an issue. On Fri, Jan 27, 2012 at 8:18 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > On Sat, Jan 28, 2012 at 3:47 AM, Alec Taylor >

Re: Feature request: read-only admin view

On Sat, Jan 21, 2012 at 1:02 AM, Chris Wilson wrote: > Hi all, > > I really like how the admin interface does a lot of the work for me in > developing a site with basic CRUD functions, and a few free bonuses > like pagination and list filtering. > > I agree with all the

Re: Ad-hoc Django integration for fault-tolerance

On Sat, Jan 28, 2012 at 3:47 AM, Alec Taylor wrote: > Thanks, hadn't thought to go with NoSQL. :) > > Quick side-note: I received 14 emails on the django-devel list between > 30 and 40 minutes ago. Strange, seeing as this one is dated 10 days > ago. Google Groups problem?

Re: MySQL connection pooling - preferred method??

Hi Cal, I'm not exactly sure what it is you're looking for. The position of the core team has been fairly clear -- there are third party connection pooling tools that handle connection pooling very well. The recommendation of the core team is that you should use these tools. The alternative is

Re: Where should this test be placed

On Fri, Jan 20, 2012 at 7:14 AM, Aaron Cannon wrote: > Hi all. > > Trying to help out with some of the Trac tickets, and wasn't sure > where tests should be placed for this ticket: > > https://code.djangoproject.com/ticket/17504 > > Is there an existing package

Re: Regarding queries cache...

On Sat, Jan 14, 2012 at 1:51 PM, "Germán M. Bravo" wrote: > Regarding queries cache... but not in the way almost everyone usually thinks > of this cache (for caching the queries results) ...but cache for the actual > queries themselves, for the query tree generated by

Re: "Current" timezone in admin

Hello Danny, On 15 janv. 2012, at 10:10, Danny W. Adair wrote: > Is there a hook that allows the "current" timezone to be set for > admin, so that it uses it for datetime display/submission? Maybe a > middleware that expects a session variable configured/named in > settings? Currently, there's

Re: Feature request: read-only admin view

+1. This feature is simple and not implies backwards compatibilities or security problems. BTW, is very useful. On Fri, Jan 20, 2012 at 3:02 PM, Chris Wilson wrote: > mins only, -- juanpex -- You received this message because you are subscribed to the Google Groups

Re: Ad-hoc Django integration for fault-tolerance

Thanks, hadn't thought to go with NoSQL. :) Quick side-note: I received 14 emails on the django-devel list between 30 and 40 minutes ago. Strange, seeing as this one is dated 10 days ago. Google Groups problem? On Wed, Jan 18, 2012 at 10:07 AM, Kenneth Reitz wrote: >

Re: MySQL connection pooling - preferred method??

Damn - no thoughts on this from anyone? On Wed, Jan 25, 2012 at 12:11 AM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: > Hi all, > > After spending about 30 minutes looking through old tickets, long > discussion threads and various blogs, I'm still not clear

MySQL connection pooling - preferred method??

Hi all, After spending about 30 minutes looking through old tickets, long discussion threads and various blogs, I'm still not clear on the MySQL connection pooling topic. To quote Russ: "the capability already exists in third party tools, and they're in a position to do a much better job at it

Triage and Reviewing

After contributing the solution to a small problem (#17492), I was inspired to look for other tickets that I would be able to help on, either by triaging un-reviewed tickets (#17537, #17561, #17573), supplying new patches (#14030*, #16735, #17186), or reviewing patches (#11305, #16955, #17541)

runserver stdout and stderr piping problems

I was launching manage.py runserver from another app and trying to capture the output correctly without luck using pipes. Eventually I narrowed the problem down to two issues. In my opinion they are bugs but I thought I'd ask for confirmations here before creating a ticket and patch. Issue 1: The

Where should this test be placed

Hi all. Trying to help out with some of the Trac tickets, and wasn't sure where tests should be placed for this ticket: https://code.djangoproject.com/ticket/17504 Is there an existing package that it would make sense to use for testing this particular bit of functionality? Thanks. Aaron --

Feature request: read-only admin view

Hi all, I really like how the admin interface does a lot of the work for me in developing a site with basic CRUD functions, and a few free bonuses like pagination and list filtering. I agree with all the comments on #820 requesting this feature (as

Model Fields to add in django.contrib.localflavor.ar

Hi, I have a models.py file to add in django.contrib.localflavor.ar This file has the same Fields as forms.py but it's to use in models. Do I need to add a ticket with the attached file? Or I have to follow another steps? César -- You received this message because you are subscribed to the

ModelForm._post_clean could simply call Model.full_clean

Hi all, I proposed this in a comment on #16423 , and then found that it had come up before: https://code.djangoproject.com/ticket/13100 https://code.djangoproject.com/ticket/13121 and was rejected thus: I think model-validation is just

Add model file to add in django.contrib.localflavor.ar

Hi, I have a models.py file to add in localflavor.ar. This file has the same Fields as forms.py but it's to use in models. Do I need to add a ticket with the attached file? Or I have to follow another steps? Thanks Cesar -- You received this message because you are subscribed to the Google

Re: Ad-hoc Django integration for fault-tolerance

Enjoy: http://guide.couchdb.org/draft/why.html -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/vQegCKmfVvAJ. To post to this group, send email to

Re: Read only Test Was: Speeding up tests

Hi, I am interested in it - could you be so nice and make this available anywhere? Thanks a lot in advance. TR Am 17.01.2012 um 12:04 schrieb Thomas Guettler: > Hi, > > same subject, but different content: > > we have a lot of tests which are read only. They don't modify the database or >

Addition of failed login signal

Greetings, As an enhancement to the existing collection of signals I wanted to propose the addition of a signal for the event of an unsuccessful login. Currently django.contrib.auth supports user_logged_in and user_logged_out for successful events. Addition of e.g. user_failed_login would allow

"Current" timezone in admin

Hi, With 1.4 timezone support I was wondering if/how django admin supports the current user's timezone. There's no corresponding HTTP header like "Accept-Language" so I guess the timezone must be set in the session (looked up from a profile or whatever). Is there a hook that allows the "current"

Regarding queries cache...

Regarding queries cache... but not in the way almost everyone usually thinks of this cache (for caching the queries results) ...but cache for the actual queries themselves, for the query tree generated by django, the Query object itself. Has anyone thought of this? Much in the same way the

Re: Don't assume that missing fields from POST data are equal to an empty string value.

I think Ian demonstrated exactly why this should not go in and that is not all forms are ModelForms. Imagine writing a REST API which allows for an optional format parameter for GET requests which is validated by a Django form. With the inclusion of this proposal all clients would be forced to

Re: Don't assume that missing fields from POST data are equal to an empty string value.

> If optional fields are > left off the HTML form deliberately, without change the Form class or > the view code, this is exactly when data loss will currently occur. > I think you are confusing optional as in "may not be specified by the > user" with optional as in "may not be processed by the

Re: Don't assume that missing fields from POST data are equal to an empty string value.

On 12 ene, 14:07, Ian Clelland wrote: > On Thu, Jan 12, 2012 at 1:02 AM, Tai Lee wrote: > > Donald, > > > Thanks for sharing your feedback with everyone. > > > I do believe that there should be some kind of validation error or at > > least a loud

Wrong annotation when using ordering in meta options

Hi, I've recently faced to an issue, which I believe is a wrong behavior. Suppose I have the following model: class ClassA(models.Model): date_f = models.DateField() char_f = models.CharField(max_length=10) And suppose I have 3 entries in this model: ('2011-11-1', string1),