Ben Stähli
Ben Stähli
couldn't there be a check if the field inherits from a multiple base field, so the `MULTIPLE`would be obsolete?
the field (widget is not really interesting/important). ``` class OfferMultipleChoiceField(ModelMultipleChoiceField): widget = OfferWidget def __init__(self, *args, **kwargs): super(OfferMultipleChoiceField, self).__init__(queryset=OfferItem.objects.all(), *args, **kwargs) ``` point is, the model/modelmultiple only makes sense if...
adding forms.ModelMultipleChoiceField to *fields.MULTIPLE would help already, and then dealing with subclasses in the .is_a method even more.
Great, thank you! As far as I can see, you'll need to become a member of the jazzband organisation on github, and transfer the repos. Before, check this https://jazzband.co/about/guidelines and...
to simplify things, you could add me or another person you trust, and I/we could do all this for you...just pinging @jezdez for a quick opinion, before we start this?...
sadly no. I guess we're all flooded with too many projects... @khashashin would you be interested to help maintain the project?
I'm not activly involved in any of the jazzband projects, but it looks promising.,..
this probably wont come through (check for example: https://stackoverflow.com/questions/5074139/how-to-get-mac-address-of-client-using-php )
This seems like a common use case, and would be nice to be configurable, without using `model.field_language` hacks, or custom templatetags. I for example, have a translated "SEO Text" field,...
anyone? this is a candidate to shot onesels in the foot...