Re: Bringing some popular must have django tools/packages under django org umbrella

2016-03-16 12:39 GMT-03:00 James Pic : > FTR, there's also Djangonauts which have been there for a while: > https://github.com/djangonauts > > This is exactly what I was asking for when I asked if there was an organization to pick on unmaintained projects. Thank you very much.

Re: FileField and ImageField

It seems like you have a pretty good grasp on the problems and possible solutions. I'm not familiar enough with storage backends and FileFields to provide much guidance so hopefully someone else can comment. Regarding the linked line in the save method which forces forward slashes, it seems

Re: Proposal: change to the way list_editable form data is submitted in the admin

I know this particular case has been discussed before. Here are two related tickets (I think there's a better canonical ticket but I can't find it just now): https://code.djangoproject.com/ticket/11652 and https://code.djangoproject.com/ticket/16549 I haven't done the required reading

Re: Override the default form field for a model field

What I meant about increasing coupling is this question: do we want to go down the road of defining more and more form related things in models? Yes, there are already a few options that are primarily for model forms (e.g. editable and blank), but is it okay to add more or should we try to

Re: Feedback on Django Channels

Hey Andrew, Thanks for looking through all that, and for the reply. I like the simplicity of your updated examples. I started to make a counter-example to suggest that `include` be inside of a `route` (https://gist.github.com/orokusaki/c0c934013ee7911071ef). But then, as I thought through

Re: Revisiting multiline tags

Here's the actual code PR https://github.com/django/django/pull/2556 On Sun, Mar 13, 2016 at 1:26 AM, Martijn van Oosterhout wrote: > > On 12 March 2016 at 05:31, Curtis Maloney wrote: > > I think this conversation needs to come to a conclusion, and that

Re: Feedback on Django Channels

On Fri, Mar 18, 2016 at 4:40 PM, Vincent wrote: > Hey Andrew, > > Thanks for looking through all that, and for the reply. > > I like the simplicity of your updated examples. I started to make a > counter-example to suggest that `include` be inside of a `route` ( >

Re: Override the default form field for a model field

A few thoughts, just to see if we can solve the problem by documenting some existing code: Would making a subclass overriding formfield() work? class RadioSelectBoolean(models.BooleanField): def formfield(self, *args, **kwargs): kwargs['widget'] = forms.RadioSelect