There is one other question I've been meaning to ask for a while. As would be expected, this FileField work adds a good amount of code to db/models/fields/__init__.py, including 3 new classes, which aren't even Fields themselves (but they're needed to make the Fields work). If I get my way, and Django gets an AudioField as well, that's two more classes, another one of which isn't a Field.
Would it make sense to move the file-related Field code into a files.py? It seems to me that it would make __init__.py considerably more manageable, as it's getting rather unruly right now. Plus, then the non-Field classes (FileProxy, File and ImageFile) could be in a module dedicated to file work, rather than being shoved in alongside all the other Fields. This is a minor point, of course, but given how much change is going on with file-related Field stuff, it makes sense to do it now, if it should be done at all. -Gul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
