Re: 1.9 release planning

2015-06-23 13:23 GMT+02:00 Loïc Bistuer : > > > On Jun 23, 2015, at 17:24, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > > > > Besides, honestly, 1.10 is just ugly :-) > > I don't really see anything wrong with 1.10+ versions but maybe that's > because

Re: use semantic versioning after 2.0?

Just want to throw in one point to consider here, pardon me if this has already been discussed in the core team. Bumping the "major version", that is moving to 2.0 instead of 1.10, will from the outside likely be seen as a larger change, regardless of whether it technically is or not. This, could

Re: Django 1.7: modelformset_factory() vs formset_factory()

On Sun, Mar 2, 2014 at 8:27 PM, Tim Graham wrote: > Yes, see https://code.djangoproject.com/ticket/17642. If you can bring > the patch up to date in the next day or two, I'll try to help review and > commit it. > A day after "the next day or two" :) but I just supplied an

Re: Django 1.7: modelformset_factory() vs formset_factory()

On Sun, Mar 2, 2014 at 8:27 PM, Tim Graham wrote: > Yes, see https://code.djangoproject.com/ticket/17642. If you can bring > the patch up to date in the next day or two, I'll try to help review and > commit it. > Thanks. I'll try to get that done. Cheers, Anders -- You

Django 1.7: modelformset_factory() vs formset_factory()

Now that formset_factory() from 1.7 accept num_min and validate_min arguments, shouldn't modelformset_factory() also support those same arguments to allow them to be passed onto formset_factory()? *Anders Steinlein* *Eliksir AS* http://e5r.no E-post: and...@e5r.no Mobil: +47 926 13 069 Twitter

Re: Change username field widget in AuthenticationForm based on USERNAME_FIELD

On Mon, Aug 5, 2013 at 10:00 PM, ptone wrote: > This seems like a reasonable change. I don't love the fact that the > contrib.auth built in forms quasi support custom user models, as it leads > to a less clear delineation about what parts of contrib.auth are tightly > coupled

Change username field widget in AuthenticationForm based on USERNAME_FIELD

to provide a patch. *Anders Steinlein* *Eliksir AS* http://e5r.no E-post: and...@e5r.no Mobil: +47 926 13 069 Twitter: @asteinlein -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving e

Re: Perception of attitude in tickets

On Mon, May 13, 2013 at 7:55 PM, Yo-Yo Ma wrote: > How about allowing comments only from the patch author and committers? >> > > The problem I see with this is that original bug reporters, aside from the > aforementioned groups, are usually the ones most engaged in

Re: Perception of attitude in tickets

On Sun, May 12, 2013 at 2:06 AM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > Looking for a positive outcome here -- my question to the community, and > especially those that feel that we've been unresponsive here: how do we > improve the situation? > I've been lurking on this

Re: Feature request: collectstatic shouldn't recopy files that already exist in destination

l contribute the patch. I know there is not a lot of time before the > feature freeze, but I'm willing to make this happen if there's interest. > Yes, please. I've been wanting this myself. This should IMHO be the default for collectstatic, but having a flag to *force* copying all files. -- *Anders Stei

Re: Django 1.5 release plans

RC 3, if needed > Dec 24 (or earlier): Django 1.5 final > Looking forward to this release, exciting! However, targeting the release for Christmas Eve seems like a bad idea PR-wise. I suggest either launching after new year's eve or quite a few days before christmas to get better/broader PR. -- *An

Re: #16455 PostGIS 2.0 support

On Mon, Aug 20, 2012 at 11:58 AM, Anssi Kääriäinen wrote: > On 13 elo, 21:25, Anssi Kääriäinen wrote: > > On 10 elo, 20:12, Jeremy Dunck wrote: > > > > I can take care of the patch. As said earlier I don't understand GIS > >