It was a busy week, especially with the DjangoCon Europe sprints. Thanks to
all participants! Look forward to reviewing the new backlog of pull
requests.
Report for week ending June 6, 2015:
Triaged
---
https://code.djangoproject.com/ticket/24885 - Writing your first Django
app, part
I believe the complaint is mostly that an invalid formset will raise a 500
whereas an invalid form (should) never. There was a patch to display an
error if not. My complaint is that this error can only occur if the dev has
rendered the form by hand missing the management form. It's likely they
woul
What about instead of trying to guess the forms from the input, just fix
the one condition which causes the error and return 0 as totalformcount +
an error marker to reraise the error in clean of the modelform?
On Friday, June 5, 2015 at 11:29:21 AM UTC+1, Patryk Zawadzki wrote:
>
> Hi folks,
>
In our case, we need to dynamically include additional "exclude" fields in
our VersionableAdmin and not override the selections the developer has set
in their subclass. There are two options to accomplished this:
1) Override get_form() which is messy because you can't just call super
here and
I don't think we should add this. Exclude is passed to the form, and we
already have a way of changing the form based on the request. I'd rather
see changes made to reduce some of the many many ways to select fields in
the admin. By my count at present we have:
ModelAdmin.fields
ModelAdmin.get_fie
Hi,
FWIW, here is how you can add real-time push to Django apps without
reinventing the world in Django (read: using blocking code):
http://crossbar.io/docs/Adding-Real-Time-to-Django-Applications/
This is using the HTTP/REST bridge services of Crossbar.io:
http://crossbar.io/docs/HTTP-Bridge-
We are writing a custom admin for CleanerVersion that subclasses ModelAdmin.
Just about every attribute has a hook method which makes extension easier. For
example, list_display has get_list_display(). However, exclude doesn't have one
implemented and it seems like an oversight. I'm proposing we
I remember that Ruby on Rails solved problem with checkboxes with a hidden
field that was added before each checkbox [1]
[1]: http://apidock.com/rails/ActionView/Helpers/FormHelper/check_box
On Friday, June 5, 2015 at 11:29:21 AM UTC+1, Patryk Zawadzki wrote:
>
> Hi folks,
>
> I've talked to Ma
