Is it too late to have the 1.3 Milestone applied to these documentation issues?
http://code.djangoproject.com/ticket/13997 http://code.djangoproject.com/ticket/11185 I'm trying to update some old code that has a custom MultiValueField and MultiWidget to be 1.2 compatible and I've never made a custom field or widget before. I have run into some issues and a Google search turns up a lot of varying quality noise from over the years. At this point, the official docs are at risk of not being in the first page for the search term "Django MultiWidget". It sure would be nice to have something authoritative from someone who understands it. More generally, as a relative newcomer to Django I have hit a frustratingly high number of commonly understood but undocumented usage patterns, incomplete and unorganized docs and general gotchas. Here is a search query I wish I had seen on day one: http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&group=milestone&component=Documentation&order=priority It gives a pretty good overview of where the official docs are lacking. I don't think I can document subclassing MultiWidget because I can't even get it to work right (in my admittedly complex use case). Some of the issues in that list seem like they would be small patches. Would it be possible to have someone mark the low hanging fruit as 1.3? If I write small documentation updates/fixes/editing for the things I've run into trouble with but now understand, will they get applied? -Paul -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
