>AFAIR unicodefication must be done before Django 1.0. This not big API >change, but some code must be changed too after it. >(Ex. str->repr or str->unicode)
Before doing it, there still is the analysis of what needs exactly to be done - for now it's just a list of keywords on the wiki page, I definitely need to put more into that page. But I am in Munich this week, so I won't be able to do much on Django stuff. The changes might introduce some backwards incompatibilities, but I don't think it will be big changes in API or something like that - so it would be fine to put all stuff that might introduce big API changes (like the descriptor fields) into magic-removal, but leave out other things like UnitOfWork (can only be done after descriptors for fields, because some of that will be needed, I think - we need to capture attribute assignements to register changed objects in the unit of work) or Unicodefication. bye, Georg
