Re: A New Design for the "Congratulations!" Page

I also give a big +1 to this. I'll really love to see this in django On 19 Apr 2017 11:05, "Adam Johnson" wrote: > A massive +1 from me too, but I'll not make any comments on design :) > > On 19 April 2017 at 09:58, Federico Capoano > wrote: > >> Looks like a great improvement for newcomers! I

Re: Improvement to objects.get_or_create and objects.update_or_create

On 27 Aug 2014 22:19, "Benjamin Scherrey" wrote: > > > You're right, it wasn't hard to implement as external code as I've already done so. The main reason why I propose it for inclusion into Django's codebase is because the new behavior is actually what I would have expected these two functions t

Re: [GSoC] Switching to Jinja2 proposal

On 15 Feb 2014 18:13, "Donald Stufft" wrote: > > > On Feb 15, 2014, at 11:43 AM, Christopher Medrela wrote: > >> My last post was pretty long and the most important questions and statements >> have left unanswered, so I will repeat them. >> >> What I'm proposing now is more conservative proposal.

RE: Proposal: Redefine specific {% block %} in an intermediate

template MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable +1 for being confusing Sent from my Windows Phone From: Carl Meyer Sent: 4/17/2013 5:37 PM To: django-developers@googlegroups.com Subject: Re: Proposal: Redefine specific {% block %}

RE: Ability to save 4xx messages to database

Hi Javier, why no Sent from my Windows Phone From: Javier Guerra Giraldez Sent: 4/11/2013 4:30 PM To: django-developers@googlegroups.com Subject: Re: Ability to save 4xx messages to database On Thu, Apr 11, 2013 at 10:21 AM, Val Neekman wrote: > Now, the $64 K question: is Django a good place for

RE: Proposal: deprecate and remove django.contrib.comments

+1 Sent from my Windows Phone From: Jacob Kaplan-Moss Sent: 3/7/2013 5:48 PM To: django-developers Subject: Proposal: deprecate and remove django.contrib.comments Hi folks -- This one's simple: I'd like to deprecate `django.contrib.comments`, scheduling it to be removed in a couple of releases.

Re: Django performance vs others

That was so long I can't even remember what I read. On 10/4/12, Jacob Kaplan-Moss wrote: > Hey folks -- > > This thread's pretty off-topic for django-dev. Can you please take it > elsewhere? Thanks. > > Jacob > > On Thu, Oct 4, 2012 at 12:49 PM, Amirouche Boubekki > wrote: >>> Are the Hello worl

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

I like this feature and have recently been thinking of implementing such on my own myself. +1 for the feature request. On 9/27/12, Dan Loewenherz wrote: > Hey all! > > This is a feature request / proposal (one which I'm willing to build out, > given that I've already developed a solution for my o

Re: Django is not a serious framework, really

I wonder why you guys are replying OP. On 4/11/12, Juan Pablo Martínez wrote: > gooby pls :) > > On Wed, Apr 11, 2012 at 10:29 AM, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >> Hi Jason, >> >> Le 11 avril 2012 14:10, Jason Ma a écrit : >> > I heavily doubted that whether t

Re: Don't assume that missing fields from POST data are equal to an empty string value.

-1 I think a programmer should not specify a field that would contain important data as optional in the first place. If the data loss from not including it in the form is going to cause problems then it should not be optional. On 1/11/12, Tai Lee wrote: > There is a potential for data loss with o

Re: prevent brute force attacks by acting on several failed logins, for example by using a captcha

+1 please On 9/29/11, Wim Feijen wrote: > Hello, > > Would it be a good idea to write a ticket and patch to stop brute > force attacks, either by requiring people to fill in a captcha after > several failed login attempts; or by setting a time delay? > > Mozilla Secure Coding Guidelines recommend

Re: please reopen ticket 15567

The correct approach is to give a "one size fits all" error message. While security is important, so also is user experience. On 9/13/11, Adam Jenkins wrote: > On Tue, Sep 13, 2011 at 12:42 PM, Wim Feijen wrote: >> Hi, thanks for your quick responses! >> >> Flavio, Jan and Florian, it only "give

Re: please reopen ticket 15567

+1 again. If a correct username and password combination are given, the person submitting the credentials should know that he doesn't have access just like cal pointed out. Its unfair and frustrating to say that the combination is wrong On 9/13/11, Cal Leeming [Simplicity Media Ltd] wrote: > +1,

Re: please reopen ticket 15567

+1 On 9/13/11, Wim Feijen wrote: > Hello, > > When a user tries to login on the admin, with correct username & > password, but is_staff is set to False, the error message is > misleadingly wrong: > > "Please enter a correct username and password. Note that both fields > are case-sensitive." > > T

Re: CSRF token not validated?

+1 On 9/12/11, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Jens, > > On 09/12/2011 10:20 AM, Jens Diemer wrote: >> >> I wonder that the CSRF token send from the client didn't be validated. > > Well, it is sanitized to only alphanumeric characters, but you're right >