Hi Christopher, I'll speak out of turn here and say I how see things from my limited experience with the project/code.
> Other issues include the broken content-types stuff (#1280... why's > that patch not checked in yet?) There hasn't been that much activity on magic-removal for the past few weeks, everyone seems to have been pretty busy. I am hoping to start some hacking again in earnest in a week's time. I'm guessing other people will be occupied with PyCon amongst other things (certainly Adrian & Jacob). As for the patch itself, I think it is OK (modulo s/get_object/get/ and some small changes), but I wanted to check with Adrian that 'packages' really are going away. > and thus broken "Show on site" links > and generic views (IIUC). Also, some of the unit tests are failing... > is that expected? I get 4 tests failing with postgres, 5 with mysql (an extra one due to an ordering thing - the 'basic' model tests need to have an order_by set on the model to make the tests more deterministic). Of the 4, 2 are manipulator related, and since manipulators need some more work, no-one has bothered to fix the tests which will probably need changing anyway. The other 2 are to do with one-to-one, and pretty much the same goes for them. > 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). I personally had a list of TODOs/issues for the bits that I was working on (new descriptor syntax): http://groups.google.com/group/django-developers/browse_frm/thread/701f1981d94e150f/5fc281a6452295b5#5fc281a6452295b5 In order to keep a vaguely working branch, I think some near-term priorities are, in order: - finish foreign key related object methods (esp .add() and .clear()) - implement the new manipulators. I don't know much about this at all. - get the admin working a bit better - #1330, #1334 (depends on manipulators) - #1346 (and probably others) - descriptor syntax for other fields (e.g. in the example article.reporter.id , you shouldn't have to do a DB lookup. Not sure if this will work in practice - this much laziness could be bad, as errors will be thrown much later, and less predictably) - big bug bash on old db lookup syntax, in (1) admin, (2) management functionality, (3) contrib apps, middleware etc. After that, I think there are things that still need a fair amount of discussion (and certainly include things I know even less about): - subclassing syntax changes: http://code.djangoproject.com/wiki/ModelInheritance - removal of 'core fields' - and the rest of the things in http://code.djangoproject.com/wiki/VersionOneFeatures :-) But all that is just my guess, in case Adrian or someone else more knowledgeable is too busy. Hope that was some help. Also, Jacob is doing Django sprint at PyCon AFAIK, which might affect all this. I'm not sure whether Jacob was planning on working on magic-removal or trunk. Luke -- "Oh, look. I appear to be lying at the bottom of a very deep, dark hole. That seems a familiar concept. What does it remind me of? Ah, I remember. Life." (Marvin the paranoid android) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
