Yes, I would like to see that in contrib.auth, which will require rewriting
the backends and introduce a auth pipeline ala django-social-auth (has/had)
-- I was planning to get some thoughts about that on DUTH. Also see this
(short) twitter discussion:
https://twitter.com/jacobian/status/651527
On Tuesday, October 27, 2015 at 12:46:47 AM UTC+1, Joey Wilhelm wrote:
>
> Fwiw, 2fa is on my short list of things to implement into my current
> project. It's a fairly important feature to me, as this is a financial
> project. And that particular implementation is precisely what I was looking
Hi everyone,
I proceeded to revert the commit for now.
Nothing prevent us from adding a warning in the future if we ever fix the
whole "blank" issue at the model level.
Simon
Le samedi 24 octobre 2015 12:29:44 UTC-4, Shai Berger a écrit :
>
> Hi,
>
> On Saturday 24 October 2015 04:13:47 chare
In 2014 I started to research if we could offer a Google Summer of Code
project aimed at improving Django's process for collecting and organizing
CLAs. I didn't complete that proposal when I found some existing solutions,
in particular https://cla.puppetlabs.com/ which Puppet labs said they were
Il 27/10/2015 17:50, Tim Graham ha scritto:
I wonder if anyone has a recommendation for a third-party solution to solve
this? Our requirements are roughly outlined below.
Not a solution but for comparison Libreoffice requests a blanket statement sent
on a public list then referenced on a wiki
I created https://code.djangoproject.com/ticket/25617 - Disallow usernames
that differ only in case in UserCreationForm.
Please voice any concerns on that ticket.
On Monday, October 26, 2015 at 2:24:27 PM UTC-4, Collin Anderson wrote:
>
> I also agree. And to be clear, we're talking about UserCr
Hm, let me check it out and get back to you. We had some migrations that
exited in failure, but with a non-0 exit status during our release. I'll
see if I can reproduce this this week.
-Ben
On Monday, October 26, 2015 at 11:21:17 AM UTC-7, Tim Graham wrote:
>
> The place you linked to is igno
+1
This sounds like a great feature, depending on the implementation.
On Monday, October 26, 2015 at 10:22:46 AM UTC-7, Tim Graham wrote:
>
> On Trac [1], Alex says, "Django did a tremendous service to its users by
> making strong password hashing be the default. The world is pushing
> forward,
BTW, there's a move afoot to reconsider removing inspect.getargspec:
http://bugs.python.org/issue20438 and http://bugs.python.org/issue25486
--Ned.
On 10/24/15 10:30 AM, Tim Graham wrote:
Here's the PR to remove 50K lines of deprecation warnings when running
the Django 1.8 tests on Python 3.5
Hi Tim,
On Wed, Oct 28, 2015 at 12:50 AM, Tim Graham wrote:
> In 2014 I started to research if we could offer a Google Summer of Code
> project aimed at improving Django's process for collecting and organizing
> CLAs. I didn't complete that proposal when I found some existing solutions,
> in par
10 matches
Mail list logo
