On Mon, 2008-03-31 at 13:45 -0500, Jacob Kaplan-Moss wrote: [...] > * Internals: not so hot; in fact, we've really only got the contributing > document. Help is needed here.
There's http://code.djangoproject.com/wiki/DevModelCreation. It needs to be updated when model inheritance lands, because the data flow in __new__ has changed slightly, but it's still predominantly accurate. I've started writing a similar page (just locally so far) for the QuerySet and Query classes. They're useful for people wanting to customise. I'd prefer stuff like that to be in subversion rather than the wiki because it's not really appropriate fodder for just anybody to edit. The trick here is walking the line between what we want to commit to and what is in existence at the moment. In the past we've used the lack of documentation as a clear sign that something isn't stable, which isn't a bad approach, but does make it annoying when you actually want to work on that stuff and don't know how it works. Prior to you posting this thread, I'd been meaning to send a query about maybe having a docs/dev/ directory which would have the status of "stuff in here is accurate, but not frozen and not public API". But now it's all your problem and you can work it out. I like that plan better. Mwahahaha... Regards, Malcolm -- Success always occurs in private and failure in full view. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
