>>If we could open a branch up to do this kind of stuff soonish, I would >>like to commit my 'mutually referential models' stuff to it first, as >>this will be touching a lot of the same code - this basically moves a >>lot of special-casing for fields out of meta/__init__.py into individual >>fields. If people don't like that code, it can be reverted, but it would >>be better than trying to merge these kinds of changes. > > > Yes, we'll do a branch for this. Are you done with the > mutually-referential-models stuff? If so, I'd like to check that into > trunk, rather than polluting the branch with anything that doesn't > have to do directly with these specific magic-removing changes. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com | chicagocrime.org >
The reason I thought this should go in the branch is that I'm not completely satisfied with it, but also I'm kind of 'stuck' with some bits of it (not really hard, just keep putting them off - there is some duplicated code to do with OneToOne and ForeignKey, some 2.4 isms, and that deleted object display stuff in the admin is kind of wierd ). It also moves around quite a lot of code. I don't think it is totally ready for the trunk, but if it got in a public branch, it would get more testing and give me the impetus to finish the rough bits....
