Hey folks, We've just started a new project here with Django and decided to build it on top of the magic-removal branch, since the project is going to be worked on for a couple of months.
Now, actually using the magic-removal is currently raising more problems than I had hoped. I've been looking into the code and trying to write and submit patches as I find problems that are easy enough to figure out, but most problems are beyond my current knowledge of the Django code, and more importantly, beyond my understanding of the design objectives of the branch. I.e. I'm fully prepared to get my hands dirty with the code, but need a bit more guidance :-P For example, <http://code.djangoproject.com/ticket/1330> is pretty much a show-stopper here. Any hints on what kind of changes would be needed to fix edit_inline on magic-removal? Other issues include the broken content-types stuff (#1280... why's that patch not checked in yet?) and thus broken "Show on site" links and generic views (IIUC). Also, some of the unit tests are failing... is that expected? Anyway, I'd be very grateful for an overview of the status of the branch, e.g. what major design issues still need to be solved and what work might need to be done that people simply don't have the time to do (and what, roughly, would be involved). Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
