On Fri, 2007-11-30 at 16:46 +0100, Patryk Zawadzki wrote:
> 2007/11/30, Adrian Holovaty <[EMAIL PROTECTED]>:
> > Without further ado, here's my list:
> >
> > * newforms-admin
> > * queryset-refactor
> > * django.newforms becomes django.forms
> > * Model-level validation
> > * Change django.templatetags not to use __path__ hacking
> > * #3591 -- Make INSTALLED_APPS an instance, and each app an instance
> > * #5361 -- File storage refactoring
> > * #285 -- WSGI SCRIPT_NAME and PATH_INFO stuff
> >
> > What am I forgetting?
>
> For my needs:
>
> * Extendable results of form_for_{instance,model} (sometimes you just
> need to override one field in a large form)
> * Sortable fields on forms extending other forms
This is the sort of thing where it wouldn't be a complete loss if it
didn't make it into 1.0, since form construction helpers are just that:
helpers. They don't depend on core changes and don't require core
changes to support them. Hence, somebody can just write something
outside of core that meets their purposes.
We're currently leaning more towards Joseph Kocherhans' replacement for
form_for_* (not sure how backwards compatible it will end up) and whilst
"nice to have", I don't see this as show stopper stuff for 1.0.
Let's keep a focus on things that require core changes (and hence can't
be done externally if not in the release).
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
