#3982: Allow Field subclasses to coerce arbitrary Python types
-----------------------------------------------------+----------------------
Reporter: Marty Alchin <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: coerce coercion | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 1 | Needs_better_patch: 1
-----------------------------------------------------+----------------------
Changes (by mtredinnick):
* owner: adrian => mtredinnick
Comment:
There's some issue drift going on here. The last patch has close to
nothing to do with the original ticket, which is essentially about helping
create Field sub-classes. Lazy instantion is not a requirement there and
is an orthogonal issue. Let's try to keep one issue per ticket, please.
I'm going to get around to tidying up the various Field sub-classing
ticket this week and I'll close this when that happens. You should open
another ticket for the lazy portion after that (probably best to wait
until then so that you can write a patch against the code that exists in
trunk).
--
Ticket URL: <http://code.djangoproject.com/ticket/3982#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
