Re: Proposal to format Django using black

2019-04-25 Thread Herman S
On Fri, Apr 19, 2019 at 6:33 PM Mariusz Felisiak wrote: > I don't think that our code style is any barrier for newcomers. As a newcomer, I can tell you that it most definitely is a barrier, at least it is for me – for the reasons laid out in my original email :) * >From what I can gather the fo

Re: Proposal to format Django using black

2019-04-25 Thread Tobias Kunze
On 19-04-25 08:24:34, Herman S wrote: >From what I gather there is a clear majority favoring Black, […] Please don't resort to influencing the discussion by way of presenting a majority opinion like that. People on django-dev are generally good at not repeating points that have been made already,

Re: Proposal to format Django using black

2019-04-25 Thread Tom Forbes
> so there is no way to know who is nodding along with which arguments. That somewhat impedes the point of posting this to get consensus, and if you ascribe to that view then all mailing list discussions about project wide changes are somewhat useless, as there could be a silent majority complet

Re: Proposal to format Django using black

2019-04-25 Thread James Bennett
I like Django's style guide. I like the *idea* of an autoformatter. I dislike the particular mostly-unconfigurable style Black enforces, and I find that several of its rules negatively impact code readability. So I would be -1 on applying it to Django. -- You received this message because you

Re: Proposal to format Django using black

2019-04-25 Thread Josh Smeaton
To answer the question about decision making... Usually a decision is made if there’s reasonable consensus in the discussion or after a vote. If no clear consensus can be reached with the core team, then a decision can be escalated to the technical board for a vote. In the future, if the core tea

Re: Proposal to format Django using black

2019-04-25 Thread Curtis Maloney
On 4/25/19 8:14 PM, James Bennett wrote: I like Django's style guide. I like the *idea* of an autoformatter. I dislike the particular mostly-unconfigurable style Black enforces, and I find that several of its rules negatively impact code readability. So I would be -1 on applying it to Django

Re: 2020 Authentication Initiativ

2019-04-25 Thread Александр Овчинников
> IMHO Django should provide a secure and simple (for developers) out of the > box solution. > I can't but agree with you. Today long (at least >15 characters [Chrome password manager], but > 20 is much better) passwords created and stored in password managers (some modern browsers include

Re: 2020 Authentication Initiativ

2019-04-25 Thread Johannes Hoppe
Auth0 looks like a need solution! And yes, I am a bit YubiKey fan myself. Use it for 2FA and PGP, worth every penny. -- On 25. Apr 2019, 17:38 +0200, Александр Овчинников , wrote: > > > IMHO Django should provide a secure and simple (for developers) out of the > > box solution. > > I can't but

Re: Support for CTAS statement with ORM API?

2019-04-25 Thread Adam Johnson
Hi Markus CTAS can be useful in some cases, but I can't imagine how we'd fit it into the Django ORM nicely. There wouldn't be a model for the correspondingly created table. Have you got a suggestion for the way you'd like to see it working? Thanks, Adam On Wed, 24 Apr 2019 at 14:03, Markus Elfr

Re: 2020 Authentication Initiativ

2019-04-25 Thread Robert Marsanyi
Many of these auth systems are client/server, not going to be the simplest thing to configure the entire stack for simple projects/tutorials/testing environments and so on. I can definitely see having.a pluggable alternative to the contrib.auth package that implements all the client-side stuff,