Re: magic-removal table name pluralization

On 1/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: On 1/6/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:> In the magic-removal branch most traces of automatic pluralization> have been removed, but the table names are still pluralized by > default. I don't think they should be. Is this just a c

Proposal: Django namespace simplification

Aaron Swartz is no diplomat but he made some good points in this rant: http://www.aaronsw.com/weblog/rewritingreddit The magic-removal branch addresses the ORM issues he raised. A remaining problem is the disorientating namespace. View modules typically begin with ugly boilerplate like: ---

Re: Proposal: django.models.core/auth should be regular apps

Ian Holsman пишет: > Hi. > I'm using packages. > I think it is a good place to put stuff like package-specific preferences. > > ie.. the preference of the text markup you would like > (bbcode/markup/textile) is stored against the 'text' package. > > if you like delicious/furl/digg is stored ag

Re: magic-removal table name pluralization

Adrian Holovaty пишет: >>In the magic-removal branch most traces of automatic pluralization >>have been removed, but the table names are still pluralized by >>default. I don't think they should be. Is this just a change that's >>meant to happen, but hasn't yet? I seem to remember a thread where >

Re: Proposal: Django namespace simplification

On Jan 7, 2006, at 6:54 AM, kmh wrote: As Aaron says, it is not obvious to the outsider what the underlying structure of the package hierarchy is. I suspect this is a common problem in projects that have evolved to meet the needs of a busy production environment. Yeah, this is a very good poi

Re: Proposal: Django namespace simplification

>One altertative to your proposal that Adrian and I tossed around at >one point was to alias certain "normal" modules into a set of >"tasks." That way writing a view would become:: +1 from me - that would allow to provide "simplified" namespaces by still keeping the basic structure in place (as

Re: magic-removal table name pluralization

On 1/7/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > Can you rehash the pros and cons for this decision? Are we going to get rid > of pluralization completely? Yes, we're getting rid of pluralization completely. It's too messy -- and beyond the scope of a Web framework -- to automate rules of th

Re: Proposal: Django namespace simplification

"Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > One altertative to your proposal that Adrian and I tossed around at one > point was to alias certain "normal" modules into a set of "tasks." That > way writing a view would become:: +1. I think this is the w

Re: magic-removal table name pluralization

Ivan Fedorov wrote: Adrian Holovaty пишет: In the magic-removal branch most traces of automatic pluralization have been removed, but the table names are still pluralized by default. I don't think they should be. Is this just a change that's meant to happen, but hasn't yet? I seem to remembe

Re: Proposal: Django namespace simplification

Jacob Kaplan-Moss wrote: > One altertative to your proposal that Adrian and I tossed around at > one point was to alias certain "normal" modules into a set of > "tasks." That way writing a view would become:: This would certainly be a vast improvement from an end-user's perspective and it would

Re: magic-removal table name pluralization

On Jan 7, 2006, at 12:51 PM, Dody Suria Wijaya wrote: Can I also vote? Or is it something reserved for the core developers? The "votes" aren't really official, but are more a way of succinctly expressing an opinion. See http://www.djangoproject.com/ documentation/contributing/#deciding-on-

Re: magic-removal table name pluralization

>expressing an opinion. See http://www.djangoproject.com/ >documentation/contributing/#deciding-on-features for a bit more on >how we use voting in the Django community. Actually rereading that stuff, I think it would be useful to have a list somewhere where you list people with commit access an

Events

What's the status on the idea of an event system for Django? I ask because I've been thinking of a more comprehensive database transitioning peice, built as a stand-alone django-app. I'd like it to be able to see when the model was updated and store info about it. Regestering for a sort of star

Re: Events

On 1/7/06, Brant Harris <[EMAIL PROTECTED]> wrote: > What's the status on the idea of an event system for Django? We've added an event system in the magic-removal branch. We're using PyDispatcher, and it's available in the django.dispatch package. Adrian -- Adrian Holovaty holovaty.com | django

Welcome to new committers for magic-removal

Over the past couple of days, we've given two more people commit access to the magic-removal branch: Russell Keith-Magee and Joseph Kocherhans. I want to take this opportunity to spell out what's happening, in the name of healthy communication and because it's important that we don't step on each

Re: magic-removal table name pluralization

hugo пишет: >>expressing an opinion. See http://www.djangoproject.com/ >>documentation/contributing/#deciding-on-features for a bit more on >>how we use voting in the Django community. > > Actually rereading that stuff, I think it would be useful to have a > list somewhere where you list people

Re: subdomain specific settings file - new idea

Daniel Poelzleithner пишет: > Amit Upadhyay wrote: > >>Hi, >> >>Wish you all a very happy and fruitful new year! >> >>Djando URL resolution causes some problem with applications hosted in >>different subdomains. Consider www.example.com >>and blog.example.com