On Wednesday, 17 January 2018 00:34:11 UTC+1, Josh Smeaton wrote:
>
> Welcome, and nice work! I've seen some of the reviews you've made and
> you're straight into the deep end.
>
Thanks Josh. Too deep maybe 🙂 — but yes.
I'm just happy to be able to work on Django. It's given me SO much.
Righ
HTTPS is enough. Despite that, how would you handle the **client** doing
decryption and encryption? I don't think this is an idea you should pursue,
especially if your expertise is not in security.
On Tuesday, 16 January 2018 10:03:00 UTC+11, Vishwas Mittal wrote:
>
> Hello everyone,
>
> I am a
Welcome, and nice work! I've seen some of the reviews you've made and
you're straight into the deep end.
On Saturday, 13 January 2018 04:01:06 UTC+11, Carlton Gibson wrote:
>
> Hi all,
>
> With help from Tim, Aymeric and Frank, I got started on the fellowship
> this week.
> (Thank you all!)
>
I updated my patch:
https://github.com/django/django/pull/9581
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-dev
Hi Collin,
Thanks, that would indeed help in my case.
The save_form_data method of the ManyToMany field would still eventually
need to be updated to have the ability to pass the through_defaults
kwarg to set(). However none of the extra fields on my intermediate
model are required so that
Hi Andrew,
Would allowing set() for through models help in your case?
https://github.com/django/django/pull/8981
Thanks,
Collin
On Mon, Jan 15, 2018 at 5:14 PM, Andrew Standley <
astand...@linear-systems.com> wrote:
> Greetings,
> I've been messing around with trying to update some custom
And I forgot; 3rd advantage:
- The 3 backend methods mentioned above won't have to take an extra
kwarg such as fallback_to_model; thus backward compatible there.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django its
Seems like I found a better keyword argument than fallback_to_model. For
the following backends setting:
AUTHENTICATION_BACKENDS = (
'django.contrib.auth.backends.ModelBackend',
'guardian.backends.ObjectBackend',
'roles.backends.RoleBackend',
)
And the ways to check:
user.has_pe
Hi,
Also there exists HTTPS devserver (at least one is
https://github.com/teddziuba/django-sslserver ) which does it's job
pretty well. Used it when had to demonstrate javascript location
services (which do require HTTPS at least on chrome).
So I'm pretty convinced that this subject can be d
