On Tue, Dec 16, 2008 at 7:07 AM, David Cramer <dcra...@gmail.com> wrote: > > I'd like to propose the addition of some useful (and common) fields in > the django core. Things like a JSONFied, YAMLField, HTMLField?, > UUIDField, etc. > > A lot of these seem like common things people use, and while many > examples are out there, it'd be nice to simply include these in core > so there's a defacto standard.
Again - you assert that these are "common things people use", yet I've never needed any of them. If you want to convince me that these are fields that many people use, implement them as a standalone project. When your standalone project can demonstrate a non-trivial user base, submit the project for consideration during the candidate feature period for a release. Of course, if this thread gets a flood of "Oh, I need that" responses, I'm also happy to be proven wrong. > Maybe at the same time, clean up the Field API if possible :) This is an entirely separate issue. If, in the process of developing your external fields project, you can present a good use case for improving the Field API and a patch for said improvements, and your suggestion is backwards compatible (or at least sensitive to the backwards compatibility issues), we're only too happy to look into integrating those changes into trunk. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
