Am Montag, 3. Dezember 2007 16:04 schrieb Marty Alchin: > 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?
I think it would be good. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
