rethinking raw_id_fields

Hello all, I was browsing the tickets and saw a few of them nagging about some restrictions to raw_id_fields. That they are limited to other objects registered in admin, that they are limited arbitrarily (relative to a regular FK) by the permissions of the user, etc. Personally, I find the little

Re: ANN: Improving our decision-making and committer process

On Thu, Sep 30, 2010 at 9:14 AM, Waylan Limberg wrote: > On Wed, Sep 29, 2010 at 7:46 PM, Russell Keith-Magee > wrote: >> On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote: >>> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev

Re: ANN: Improving our decision-making and committer process

On Wed, Sep 29, 2010 at 7:46 PM, Russell Keith-Magee wrote: > On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote: >> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote: >> >>> My suggestion is about this unfortunate ticket status -- 'Accepted'.

Re: ANN: Improving our decision-making and committer process

On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote: > On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote: > >> My suggestion is about this unfortunate ticket status -- 'Accepted'. >> This now works as a sort of a dusty shelf: when anyone of the core team >> looks at the

Re: ANN: Improving our decision-making and committer process

On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote: > My suggestion is about this unfortunate ticket status -- 'Accepted'. > This now works as a sort of a dusty shelf: when anyone of the core team > looks at the patch and decides that there's nothing wrong with it he > puts it on that

Re: ANN: Improving our decision-making and committer process

On 09/30/2010 01:40 AM, Chuck Harmston wrote: In my world, the "accepted" status should only be used in one circumstance: when a person is actively developing under or maintaining a patch for the ticket. It's an indicator that someone has taken ownership of a ticket, to prevent duplication of

Re: ANN: Improving our decision-making and committer process

In my world, the "accepted" status should only be used in one circumstance: when a person is actively developing under or maintaining a patch for the ticket. It's an indicator that someone has taken ownership of a ticket, to prevent duplication of effort, etc. For example, I accepted ticket #25

Re: ANN: Improving our decision-making and committer process

Hello Jacob and everyone. On 09/29/2010 09:59 PM, Jacob Kaplan-Moss wrote: Starting today, we're going to be making some minor but significant changes to the way the Django core committer team "does business." That's about time :-). Congratulations and thank you! I have a comment and a

Re: A few thoughts on Process 2 cents

Sorry about that. I was actually kind of interested in whether the 'process' aspect of admin (and possibly other contrib apps?) had undergone any changes, given that I've heard some sentiment about people hoping contrib was 'approaching zero'. -Steve On Sep 29, 4:39 pm, Jacob Kaplan-Moss

Re: A few thoughts on Process 2 cents

On Wed, Sep 29, 2010 at 3:21 PM, subs...@gmail.com wrote: > Speaking of which... who is interested in admin these days? Been > trying to scare up some feedback @ http://code.djangoproject.com/ticket/5833 > for some time now. Please don't derail threads with unrelated topics

Re: A few thoughts on Process 2 cents

Speaking of which... who is interested in admin these days? Been trying to scare up some feedback @ http://code.djangoproject.com/ticket/5833 for some time now. On Sep 29, 2:39 pm, Jacob Kaplan-Moss wrote: > sense to have more area-specific committers. If someone's

Re: be localflavor Belgium

I added a new patch to the ticket with the following changes: add support for 0, 04 phone number format. Wrap long lines. Laurent On Sep 29, 11:23 am, Gert Van Gool wrote: > IMHO I would allow a non-spaced version. My typing my phone number as > 0498725202

Re: Class based models

Hmm... I do see what you're saying. The line in question, however, should respect subclasses. So your example wouldn't fail in the case of a proper subclass. I checked out that thread and I saw Russel commented on it and ironically he mentioned contrib.comments as well. One thing you say is

Re: A few thoughts on Process 2 cents

On Wed, Sep 29, 2010 at 1:34 PM, dartdog wrote: > So maybe subdividing the areas of responsibility might help? I know it > is generally recognized that certain comitters have specific expertise > but it might make it easier to shore up some of the bus areas like the > orm as

A few thoughts on Process 2 cents

I attended a Wordcamp recently (yeh, the dark side) but I was very interested that they only have 7-8 core comitters they add feature specific people for short, release cycles for specific features,, that sounds sort of odd,, but I think the most interesting thing was that that sub divide the

Re: be localflavor Belgium

IMHO I would allow a non-spaced version. My typing my phone number as 0498725202 should also work. Second thing, wrap the long lines :) Relevant ticket is #14349 (http://code.djangoproject.com/ticket/14349) -- Gert Mobile: +32 498725202 Twitter: @gvangool Web:

ANN: Improving our decision-making and committer process

Hi folks -- Starting today, we're going to be making some minor but significant changes to the way the Django core committer team "does business." Put simply, we're changing the way we make decisions so that we can make important policy and design calls more quickly and easily. In a nutshell: *

be localflavor Belgium

Hello, I created a patch to add support for Belgium to localflavor. I attached the patch to a ticket which is marked as accepted. The patch contains the forms fields, unit tests and the doc changes. What do I need to do next ? Wait for someone to review the patch and commit it ? Laurent --

Re: #12012 Logging: request for comments

On Wed, Sep 29, 2010 at 5:43 PM, Ian Lewis wrote: > Not sure I ever understood what Bikeshedding means properly, but fair > enough. For the history and meaning of the term, see here: http://bikeshed.com/ Yours, Russ Magee %-) -- You received this message because you are

Re: [Contact form] change Ukrainian locale

The language code for Ukranian is uk: http://www.iana.org/assignments/language-subtag-registry Type: language Subtag: uk Description: Ukrainian Added: 2005-10-16 Suppress-Script: Cyrl UA is the country code for the Ukraine. Cheers Tom On Wed, Sep 29, 2010 at 2:44 PM, Jeremy Dunck

Re: [Contact form] change Ukrainian locale

On 29.09.2010, at 15:44, Jeremy Dunck wrote: > Oleksandr, > I've forwarded this to django-developers@googlegroups.com which is > the more appropriate forum. > > Please join that list to participate in the discussion. > > On Wed, Sep 29, 2010 at 8:31 AM, wrote: >>

Re: Application, tempaltetags and namespace

Cool, than from what i see it seems the namespacing will be more and more implemented in Django in the future. But as a good practice, it would be cool if it's finally happen to force any templatetags to be used with namespace ? Cause if people can use the old way to do things, we'll still have

Re: No caching if request.GET not empty

Hi Thomas, there is a ticket for that: http://code.djangoproject.com/ticket/4992 On 29 сен, 16:36, Thomas Guettler wrote: > Hi, > > I got not response on django-users, now I ask here: > > requests with a query string (http://example.com?foo=bar) are not cached in > Django:

No caching if request.GET not empty

Hi, I got not response on django-users, now I ask here: requests with a query string (http://example.com?foo=bar) are not cached in Django: http://code.djangoproject.com/browser/django/trunk/django/middleware/cache.py {{{ if not request.method in ('GET', 'HEAD') or request.GET:

Re: #12012 Logging: request for comments

Not sure I ever understood what Bikeshedding means properly, but fair enough. My point was more to break it up the logging level by 2/3/400 classes of HTTP status codes and log each status code class with the same logging level. On Wed, Sep 29, 2010 at 1:06 AM, Alex Gaynor