I've used and would like to see at least JSONField and/or PickleField
in contrib/core. Here's a link to my current implementation.
http://dpaste.com/hold/100270/
If it's not going to make it into contrib/core, I'd welcome any
suggestions, improvements or alternative implementations.
Cheers.
Tai
On Mon, 2008-12-15 at 14:07 -0800, David Cramer 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
On Tue, Dec 16, 2008 at 7:07 AM, David Cramer 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
Make app.
Post on Google Code (or other site)
Profit!
:)
These shouldn't need to be in core to be used.
--
Collin Grady
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this g
Ya core/contrib (same thing to me).
My biggest issue with custom fields at the moment is the fact that the
hooks aren't really the best. JSONField/etc have to use ugly signals
to allow any data-type to be used.
On Dec 15, 4:12 pm, "Mike Axiak" wrote:
> I'd much rather see a contrib app for thes
I'd much rather see a contrib app for these. E.g.::
from django.contrib.datafields import fields as datafields
class MyModel(models.Model):
my_yaml = datafields.YAMLField()
...
and any refactoring that's necessary to facilitate this cleaning should be
dealt with. (And I thin
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
