On Fri, Oct 3, 2008 at 9:48 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Think "interfaces". Given that you wrote the file storage stuff and are > no doubt aware that we still have lots of fuzzy issues where something > may or may not be able to be used where a Python file object is used, > you can probably see that there are some uses for this.
Yeah well, I notice a conspicuous lack of any File ABC. ;) I have a feeling they're still working out how many flavors to have (ReadableFile, WriteableFile, SeekableFile, etc.) before including it, but I don't know for sure, obviously. > There may well be a plan. I, personally, don't have a plan right this > minute because Python 2.6 is too new and is just one of many Python > versions we support. Trying to predict the future in open source is > generally going to be hard. All you can really do is put in a note > saying "this is accurate as of this date" (something that's been > unfortunately lacking in previous Django books, so please convince your > editor to put something in of that nature). Yeah, understood. Having 1.0 out the door helps tremendously, because I can target a very stable version with a clear number to work from. I'll make sure it's plainly labeled though. :) -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 -~----------~----~----~----~------~----~------~--~---
